[Bug 47715] New: Maximized Window size and location is incorrect if overridden by WM_GETMINMAXINFO or SetWindowPos

[wine-bugs at winehq.org]

https://bugs.winehq.org/show_bug.cgi?id=47715

            Bug ID: 47715
           Summary: Maximized Window size and location is incorrect if
                    overridden by WM_GETMINMAXINFO or SetWindowPos
           Product: Wine
           Version: unspecified
          Hardware: x86
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: user32
          Assignee: wine-bugs at winehq.org
          Reporter: danweiss at gmail.com
      Distribution: ---

Created attachment 65185
  --> https://bugs.winehq.org/attachment.cgi?id=65185
Example WIN32 program that demonstrates the bug

Tested on Wine Staging 4.14 on MX Linux.

On Windows, you can use WM_GETMINMAXINFO, then a maximized window will appear
with a specified size and location.  Even though the window is considered
Maximized, it is not necessarily covering up the whole screen.

You can also use SetWindowPos to move the maximized window to a specific
location and size.

After calling SetWindowPos, the window will immediately move and resize.  The
next time the window is restored, then maximized, it will snap back to the
coordinates specified in WM_GETMINMAXINFO.



When I run the test program on Windows 10, it create the window at location
(256,256), with size 256x256, then moves it to location (512,256).

When I try this on Wine, Maximized means maximized, and the window fills the
entire region that a maximized program would occupy.  It does not take into
account the maximized size specified in WM_GETMINMAXINFO or SetWindowPos.


Related bugs: 5941

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.