BUG: SetWindowPlacement and ptMin.x or ptMax.x = -1

ID: Q110793

The information in this article applies to:

SYMPTOMS

Passing an X coordinate value of -1 to SetWindowPlacement causes the parameter to be ignored. If ptMinPosition.x is set to -1, SetWindowPlacement won't reset the minimized window coordinate; this is also true for ptMaxPosition.x. This was undocumented in the Windows 3.1 SDK documentation.

CAUSE

This problem is caused by the use of -1 as a special value. A value of -1 in the X coordinate causes the API (application programming interface) to use the window's current coordinate for the specified parameter.

RESOLUTION

Microsoft has confirmed this to be a bug in the products list above.

This behavior may be a problem for application developers because they may want to set the maximized or minimized horizontal coordinate of a window to -1. To avoid this problem, the developer should trap values of -1, and use a value of -2 or 0 (zero) as appropriate.

Additional query words:

Keywords          : kbNTOS kbGrpUser kbWinOS kbWndw kbWndwProp 
Issue type        : kbbug

Last Reviewed: January 2, 1999