- 06 Oct, 2020 16 commits
-
-
Nikolay Sivov authored
Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=49946Signed-off-by:
Nikolay Sivov <nsivov@codeweavers.com> Signed-off-by:
Alexandre Julliard <julliard@winehq.org>
-
Zebediah Figura authored
Signed-off-by:
Zebediah Figura <z.figura12@gmail.com> Signed-off-by:
-
Zebediah Figura authored
Signed-off-by:
-
Zebediah Figura authored
Signed-off-by:
-
Zebediah Figura authored
Signed-off-by:
-
Michael Stefaniuc authored
Signed-off-by:
Michael Stefaniuc <mstefani@winehq.org> Signed-off-by:
-
Michael Stefaniuc authored
Signed-off-by:
-
Michael Stefaniuc authored
Signed-off-by:
-
Michael Stefaniuc authored
Signed-off-by:
-
Michael Stefaniuc authored
Signed-off-by:
-
Michael Stefaniuc authored
Signed-off-by:
-
Michael Stefaniuc authored
Signed-off-by:
-
Michael Stefaniuc authored
Signed-off-by:
-
Michael Stefaniuc authored
Signed-off-by:
-
Michael Stefaniuc authored
Signed-off-by:
-
Michael Stefaniuc authored
Signed-off-by:
-
- 05 Oct, 2020 24 commits
-
-
Gijs Vermeulen authored
Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=49873Signed-off-by:
Gijs Vermeulen <gijsvrm@gmail.com> Signed-off-by:
Piotr Caban <piotr@codeweavers.com> Signed-off-by:
-
Alistair Leslie-Hughes authored
Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=49911Signed-off-by:
Alistair Leslie-Hughes <leslie_alistair@hotmail.com> Signed-off-by:
-
Rémi Bernon authored
If the current thread isn't the foreground thread. Otherwise we may clip the cursor in the wrong thread, that isn't expecting mouse messages or may not be checking its messages. Red Faction has some race condition where this can happen for instance, with clip_fullscreen_window called from X11DRV_DisplayDevices_Update callback in a background thread. This thread starts clipping the cursor, and the foreground thread isn't receiving MotionNotify events anymore. Signed-off-by:
Rémi Bernon <rbernon@codeweavers.com> Signed-off-by:
-
Rémi Bernon authored
The message was sent to two different types of windows, with a different semantic. We can now add parameters to the request without changing the notify parameters semantics. Signed-off-by:
-
Sven Baars authored
Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=49904Signed-off-by:
Sven Baars <sbaars@codeweavers.com> Signed-off-by:
-
Sven Baars authored
Signed-off-by:
-
Nikolay Sivov authored
Signed-off-by:
-
Nikolay Sivov authored
Signed-off-by:
-
Nikolay Sivov authored
Signed-off-by:
-
Nikolay Sivov authored
Signed-off-by:
-
Nikolay Sivov authored
Signed-off-by:
-
Nikolay Sivov authored
Signed-off-by:
-
Nikolay Sivov authored
Signed-off-by:
-
Nikolay Sivov authored
Signed-off-by:
-
Nikolay Sivov authored
Signed-off-by:
-
Daniel Lehman authored
Signed-off-by:
Daniel Lehman <dlehman25@gmail.com> Signed-off-by:
-
Daniel Lehman authored
Signed-off-by:
-
Zhiyi Zhang authored
Once Alt+Enter handling is implemented, the fullscreen state may change without dxgi necessarily being aware of it. Signed-off-by:
Zhiyi Zhang <zzhang@codeweavers.com> Signed-off-by:
Henri Verbeet <hverbeet@codeweavers.com> Signed-off-by:
-
Zhiyi Zhang authored
Signed-off-by:
-
Zhiyi Zhang authored
Signed-off-by:
-
Zhiyi Zhang authored
Signed-off-by:
-
Zhiyi Zhang authored
Signed-off-by:
-
Martin Storsjo authored
When a signal is raised in a leaf function (that hasn't backed up the Lr register itself), we need to restore both Pc and Lr separately. This doesn't seem to be possible via libunwind, so add a special case unwinding rule for this function. As we have a special case for the function, we could also just as well skip normal dwarf unwinding for this function altogether and just restore the full context from the stack. Signed-off-by:
Martin Storsjo <martin@martin.st> Signed-off-by:
-
Martin Storsjo authored
Try to keep the behaviour from ea9f47a7 of erroring out if unwinding ends up out of bounds (with pc==lr, where setting pc to lr doesn't progress the unwind), but support unwinding from functions without unwind info. Signed-off-by:
-
