From: Руслан Ижбулатов Date: Thu, 26 Jan 2017 17:44:01 +0000 (+0000) Subject: GDK W32: Different maximized window position for non-CSD windows X-Git-Tag: archive/raspbian/3.24.39-1+rpi1~1^2~65^2~39^2~830 X-Git-Url: https://dgit.raspbian.org/?a=commitdiff_plain;h=dca4f1e715610a3f42826fb7ba1cdc3bc0df319c;p=gtk%2B3.0.git GDK W32: Different maximized window position for non-CSD windows It seems that WM interprets the same MINMAXINFO contents differently depending on which styles the window has. Play along. https://bugzilla.gnome.org/show_bug.cgi?id=765161 --- diff --git a/gdk/win32/gdkevents-win32.c b/gdk/win32/gdkevents-win32.c index 611cb07e01..6dc379fe00 100644 --- a/gdk/win32/gdkevents-win32.c +++ b/gdk/win32/gdkevents-win32.c @@ -2204,8 +2204,25 @@ _gdk_win32_window_fill_min_max_info (GdkWindow *window, * window will actually end up. * "0" here is the top-left corner of the primary monitor. */ - mmi->ptMaxPosition.x = 0 + (nearest_info.rcWork.left - nearest_info.rcMonitor.left); - mmi->ptMaxPosition.y = 0 + (nearest_info.rcWork.top - nearest_info.rcMonitor.top); + /* An investigation into bug 765161 turned up a weird Windows WM behaviour + * where it would interpret "0:0" as "top-left of the workea" (accounting for a taskbar + * possibly being along the left/top edge of the screen) when window has styles + * (i.e. not CSD), and interpret the same "0:0" as "top-left of the screen" (not + * accounting for a taskbar) when window has no styles (i.e. a CSD window). + * This doesn't seem to be documented anywhere. + * The following code uses a simple CSD/non-CSD test, but it could be that + * this behaviour hinges on just one particular window style. + * Finding exactly which style that could be is not very useful for GTK, however. + */ + mmi->ptMaxPosition.x = 0; + mmi->ptMaxPosition.y = 0; + + if (_gdk_win32_window_lacks_wm_decorations (window)) + { + mmi->ptMaxPosition.x += (nearest_info.rcWork.left - nearest_info.rcMonitor.left); + mmi->ptMaxPosition.y += (nearest_info.rcWork.top - nearest_info.rcMonitor.top); + } + mmi->ptMaxSize.x = nearest_info.rcWork.right - nearest_info.rcWork.left; mmi->ptMaxSize.y = nearest_info.rcWork.bottom - nearest_info.rcWork.top; }