- 09 Sep, 2019 2 commits
-
-
Alexandre Julliard authored
Signed-off-by:Alexandre Julliard <julliard@winehq.org>
-
Alexandre Julliard authored
Signed-off-by:
-
- 08 Sep, 2019 5 commits
-
-
Alexandre Julliard authored
Signed-off-by: -
Alexandre Julliard authored
Signed-off-by: -
Alexandre Julliard authored
Signed-off-by: -
Alexandre Julliard authored
Signed-off-by: -
Alexandre Julliard authored
Signed-off-by:
-
- 06 Sep, 2019 25 commits
-
-
Jacek Caban authored
Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=47675Signed-off-by:
Jacek Caban <jacek@codeweavers.com> Signed-off-by:
-
Sven Baars authored
Signed-off-by:
Sven Baars <sven.wine@gmail.com> Signed-off-by:
-
Sven Baars authored
Signed-off-by:
-
Zebediah Figura authored
Signed-off-by:
Zebediah Figura <z.figura12@gmail.com> Signed-off-by:
-
Evgeny Litvinenko authored
Signed-off-by:
Evgeny Litvinenko <evgeny.v.litvinenko@gmail.com> Signed-off-by:
-
Rémi Bernon authored
Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=40606Signed-off-by:
Rémi Bernon <rbernon@codeweavers.com> Signed-off-by:
-
Rémi Bernon authored
XWarpPointer will always succeed, regardless of grabs, so if the pointer is already grabbed, by some other application, we should not ask to warp it. Signed-off-by:
Huw Davies <huw@codeweavers.com> Signed-off-by:
-
Rémi Bernon authored
Signed-off-by:
-
Rémi Bernon authored
This flag should only indicate a successful call to XGrabPointer. If not then we could assume we have ownership of the pointer when we don't. Signed-off-by:
-
Rémi Bernon authored
As we ignore these NotifyGrab / NotifyUngrab w.r.t focus decisions, some applications are unaware of mouse grabs being lost and sometimes cursor clipping is lost. We have to keep the last clip rectangle and restore it when grab is released. This has been squashed with the foreground window check from Zhiyi Zhang <zzhang@codeweavers.com> to fix an issue that happens when switching from a fullscreen window - because there's some additional focus events involved - but in general, if the window that is getting focus cannot be activated: When FocusIn/NotifyWhileGrabbed is received, SetForegroundWindow is not called if the window cannot be activated. When the FocusIn/NotifyUngrab event arrives for the same window, we have to check the foreground window before restoring cursor clipping rectangle. For reference, the event sequence when pressing Alt-Tab - for WMs that grab the keyboard - is the following: 1. FocusOut/NotifyGrab, when WM grabs the keyboard. 2. FocusOut/NotifyWhileGrabbed, while WM switches windows, this calls SetForegroundWindow(GetDesktopWindow()). The event sequence for normal windows ends here, but for fullscreen windows, there may be these additional events: 3. FocusIn/NotifyWhileGrabbed, which may not change Wine foreground window if it cannot be activated. 4. FocusIn/NotifyUnGrab, when WM releases the keyboard while switching windows, this is ignored but it should not retry to grab the cursor, because window is not foreground. 5. FocusOut/NotifyNormal, when WM finishes switching the windows. Signed-off-by:
-
Rémi Bernon authored
When the window manager has taken a keyboard grab, it may be going to move the window itself, so the application should not move the cursor at the same time. Signed-off-by:
-
Rémi Bernon authored
Several window managers are sending FocusOut with NotifyGrab mode then FocusOut with NotifyWhileGrabbed mode when a window focus is lost, as a consequence of grabbing the keyboard input before changing window focus. This is the case during alt-tab, but keyboard can also be grabbed when bringing activity view or clicking on the title bar. In this cases NotifyWhileGrabbed events aren't sent until the window really loses foreground. In the same manner, when focus is restored, they usually send FocusIn with NotifyWhileGrabbed mode followed by FocusIn with NotifyUngrab mode when the keyboard grab is released. When bringing activity view back and forth, or clicking on the title bar, only NotifyUngrab event will be sent. In order to be consistent across WM and to help simplifying focus handling, just ignore focus events related to keyboard grabs. Signed-off-by:
-
Michael Stefaniuc authored
Signed-off-by:
Michael Stefaniuc <mstefani@winehq.org> Signed-off-by:
Henri Verbeet <hverbeet@codeweavers.com> Signed-off-by:
-
Gabriel Ivăncescu authored
In the Windows vbscript parser, some End statements don't require a newline preceeding them. The game Ymir actually depends on this. Signed-off-by:
Gabriel Ivăncescu <gabrielopcode@gmail.com> Signed-off-by:
-
Jactry Zeng authored
Signed-off-by:
Jactry Zeng <jzeng@codeweavers.com> Signed-off-by:
Nikolay Sivov <nsivov@codeweavers.com> Signed-off-by:
-
Dmitry Timoshkov authored
Some print monitors are very sensitive to loads/unloads being done in a quick succession like AddMonitor() does, and that even leads to crashes because the monitor I have here creates a thread on load and when the thread starts - the monitor dll is already unloaded. A solution to this is moving the monitor unloading to DeleteMonitor. Signed-off-by:
Dmitry Timoshkov <dmitry@baikal.ru> Signed-off-by:
-
Dmitry Timoshkov authored
Signed-off-by:
-
Dmitry Timoshkov authored
Signed-off-by:
-
Alistair Leslie-Hughes authored
Signed-off-by:
Alistair Leslie-Hughes <leslie_alistair@hotmail.com> Signed-off-by:
-
Alistair Leslie-Hughes authored
Signed-off-by:
-
Zebediah Figura authored
Signed-off-by:
-
Zebediah Figura authored
Signed-off-by:
-
Zebediah Figura authored
Signed-off-by:
-
Zebediah Figura authored
Signed-off-by:
-
Zebediah Figura authored
Signed-off-by:
-
- 05 Sep, 2019 8 commits
-
-
Alistair Leslie-Hughes authored
Signed-off-by:
-
Alex Henrie authored
Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=45560Signed-off-by:
Alex Henrie <alexhenrie24@gmail.com> Signed-off-by:
-
Alex Henrie authored
Signed-off-by:
-
Alex Henrie authored
Signed-off-by:
-
Alex Henrie authored
Signed-off-by:
-
Dmitry Timoshkov authored
AddMonitor dereferences pMonitors later without any checks. Signed-off-by:
-
Alistair Leslie-Hughes authored
Signed-off-by:
Andrew Eikum <aeikum@codeweavers.com> Signed-off-by:
-
Huw Davies authored
Fixes build error on macOS introduced by commit 96820142Signed-off-by:
-
