[PATCH v5 0/1] MR1153: winex11.drv: Correctly handle clipping for fullscreen windows.

[Gabriel Ivăncescu]

When we are clipping (due to fullscreen), certain operations are bugged (such as creating another window on top, grabbing the window during a size-move operation, changing mouse capture, etc) so we must temporarily unclip first.

Seems unclipping it temporarily during such operation is enough to fix this.

This probably wasn't very obvious in practice because most times "fullscreen" means a single non-resizeable window with no menus and so on (e.g. fullscreen games), but that's not always the case.

--
  v5: win32u: Don't clip fullscreen windows while capturing mouse pointer.
 
https://gitlab.winehq.org/wine/wine/-/merge_requests/1153

[PATCH v5 1/1] win32u: Don't clip fullscreen windows while capturing mouse pointer.

[Gabriel Ivăncescu]

From: Gabriel Ivăncescu <gabrielopcode(a)gmail.com>

Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=53831
Signed-off-by: Gabriel Ivăncescu <gabrielopcode(a)gmail.com>
---
 dlls/win32u/input.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/dlls/win32u/input.c b/dlls/win32u/input.c
index 1dcc439e560..0c462f42675 100644
--- a/dlls/win32u/input.c
+++ b/dlls/win32u/input.c
@@ -2486,6 +2486,7 @@ BOOL clip_fullscreen_window( HWND hwnd, BOOL reset )
 
     if (!NtUserGetWindowRect( hwnd, &rect )) return FALSE;
     if (!NtUserIsWindowRectFullScreen( &rect )) return FALSE;
+    if (get_capture()) return FALSE;
     if (NtGetTickCount() - thread_info->clipping_reset < 1000) return FALSE;
     if (!reset && clipping_cursor && thread_info->clipping_cursor) return FALSE;  /* already clipping */
 
-- 
GitLab

https://gitlab.winehq.org/wine/wine/-/merge_requests/1153