[Bug 37864] New: When I resize a maximized MDI window it assumes the new size instead of remaining maximized
https://bugs.winehq.org/show_bug.cgi?id=37864 Bug ID: 37864 Summary: When I resize a maximized MDI window it assumes the new size instead of remaining maximized Product: Wine Version: 1.6.2 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ryampolsky(a)yahoo.com Distribution: --- Created attachment 50431 --> https://bugs.winehq.org/attachment.cgi?id=50431 Screenshot showing a maximized MDI child after resizing 'unmaximizes' it. My app is a 'smart terminal' that supports multiple sessions in MDI windows. The size of the MDI child windows can be changed by the app running on the server, so at the end of each transaction, if the app has changed the window dimenensions, I resize the window. If my MDI window is maximized, this has no effect on a Windows system (except that if I later unmaximize the MDI child, it will display at the correct new size). But on recent WINE builds (Linux and Mac), when I resize the MDI child, the window assumes the new size, even though it's techincally in the 'mdi maximized' state (i.e., the MDI buttons are still there on the menubar. If I switch between MDI children, they get redrawn correctly maximized (including the one I just resized). I coded a workaround in my app where I don't resize the window if it's maximized, and that seems to work okay under WINE (though I guess the new size info is getting lost). In any case, that verifies that the problem is definitely happening in response to my resize operation. F.Y.I., my resize operation uses SetWindowPlacement() to change the position and size of the window - specifically because I don't want it to affect the window if it's minimized or maximized. Only if it's in the normal state. It's been a long time since I wrote this code, but again, it's always worked on all versions of Windows. I have a feeling it might have worked a while back in WINE - though I rarely run maximized, so I may have just recently noticed a bug that's always been there... Here's the basic code logic. SizeWindowForScreenDimentions calls SetWindowPlacement based on the size calculated for the new row/column grid. The code below has the workaround that prevents the problem in WINE. Also attached a screenshot showing the unmaximized children with the MDI buttons still on the menubar. // If base screen dimensions don't match prior dimensions, resize the window here. // (unless mdi-maximized, in which case, doing this unmaximizes in WINE) if (!mdi_maximized) { if ((rows != old_rows) || (cols != old_cols)) { SizeWindowForScreenDimensions(scr, rows, cols, &resizeable); } } // In case window was hidden under an initial popup, show it now. ShowWindow(scr->hScreenWnd, SW_SHOW); -- 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.
https://bugs.winehq.org/show_bug.cgi?id=37864 --- Comment #1 from ryampolsky(a)yahoo.com --- More info on the SizeWindowForScreenDimensions() function - which is where the problem's really happening. All it does is call GetWindowPlacement(), update the rcNormalPosition rectangle in the WINDOWPLACEMENT struct and then call SetWindowPlacement() to change the position rect. I verified that the WINDOWPLACEMENT showCmd field returned by GetWindowPlacement() is 3 (SW_MAXIMIZE). When I call SetWindowPlacement with showCmd of SW_MAXIMIZE, it should remain maximized. I think that's where the WINE bug is. After that call, the MDI child window size and position reflects the new rcNormalPosition, but the window is still technically 'maximized' (i.e., the MDI child buttons appear both on the menubar and on the MDI child's titlebar). And if I click on a second MDI child (now visible, because the original one isn't properly maximized), it comes up maximized, and everything's okay from there on - until it happens again after the next transaction. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=37864 ryampolsky(a)yahoo.com changed: What |Removed |Added ---------------------------------------------------------------------------- Component|-unknown |gdi32 -- 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.
https://bugs.winehq.org/show_bug.cgi?id=37864 joaopa <jeremielapuree(a)yahoo.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jeremielapuree(a)yahoo.fr --- Comment #2 from joaopa <jeremielapuree(a)yahoo.fr> --- Does the bug still occur with wine-5.11? -- 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.
https://bugs.winehq.org/show_bug.cgi?id=37864 Ken Sharp <imwellcushtymelike(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |Abandoned? -- 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.
participants (2)
-
wine-bugs＠winehq.org -
WineHQ Bugzilla