- 25 Jun, 2020 6 commits
-
-
Rémi Bernon authored
This delivers the rawinput messages to the correct process, regardless of where the input was received. As for now RIDEV_INPUTSINK is still not implemented, this only fixes the case where input is injected in a background process and where it should not receive rawinput -as in the test- or when cursor moves over a background window and the foreground process should have received rawinput messages. Signed-off-by:
Rémi Bernon <rbernon@codeweavers.com> Signed-off-by:
Alexandre Julliard <julliard@winehq.org>
-
Rémi Bernon authored
Another thread is created to execute the tests, for SetThreadDesktop to succeed consistently. It seems to fail spuriously if it is called from a thread that already created some windows before. This shows that rawinput messages may be dispatched across desktops, but only if the subscribing process has a window in the input desktop, and it is the foreground process (even if the target window may be in another desktop). Signed-off-by:
-
Zebediah Figura authored
Oddly, Windows doesn't either. Signed-off-by:
Zebediah Figura <z.figura12@gmail.com> Signed-off-by:
-
Zebediah Figura authored
To match Windows. Signed-off-by:
-
Zebediah Figura authored
Signed-off-by:
-
Zebediah Figura authored
Signed-off-by:
-
- 24 Jun, 2020 30 commits
-
-
Paul Gofman authored
Signed-off-by:
Paul Gofman <pgofman@codeweavers.com> Signed-off-by:
-
Paul Gofman authored
Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=49007 Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=49098 Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=49041Signed-off-by:
-
Gabriel Ivăncescu authored
Signed-off-by:
Gabriel Ivăncescu <gabrielopcode@gmail.com> Signed-off-by:
Jacek Caban <jacek@codeweavers.com> Signed-off-by:
-
Gabriel Ivăncescu authored
Signed-off-by:
-
Gabriel Ivăncescu authored
Signed-off-by:
-
Nikolay Sivov authored
Signed-off-by:
Nikolay Sivov <nsivov@codeweavers.com> Signed-off-by:
-
Nikolay Sivov authored
Signed-off-by:
-
Nikolay Sivov authored
Signed-off-by:
-
Nikolay Sivov authored
Signed-off-by:
-
Paul Gofman authored
Signed-off-by:
-
Huw Davies authored
Signed-off-by:
Huw Davies <huw@codeweavers.com> Signed-off-by:
-
Huw Davies authored
Signed-off-by:
-
Huw Davies authored
Signed-off-by:
-
Huw Davies authored
Otherwise, under Wine, win_skip() counts as a failure. Signed-off-by:
-
Hans Leidekker authored
Signed-off-by:
Hans Leidekker <hans@codeweavers.com> Signed-off-by:
-
Hans Leidekker authored
Signed-off-by:
-
Hans Leidekker authored
Signed-off-by:
-
Hans Leidekker authored
Signed-off-by:
-
Hans Leidekker authored
Signed-off-by:
-
Hans Leidekker authored
Signed-off-by:
-
Hans Leidekker authored
Signed-off-by:
-
Hans Leidekker authored
Signed-off-by:
-
Rémi Bernon authored
CoD: Black Ops 3 and CoD: WWII modify these (and several others) and expect to have enough space for a few instructions. It then verifies later that the patches are still in place, and terminates if the byte sequence do not match. Having small symbols can make the patches to overlap and the check to fail. Signed-off-by:
-
Alexandre Julliard authored
Signed-off-by: -
Alexandre Julliard authored
Signed-off-by: -
Vijay Kiran Kamuju authored
Signed-off-by:
Vijay Kiran Kamuju <infyquest@gmail.com> Signed-off-by:
-
Vijay Kiran Kamuju authored
Signed-off-by:
-
Alistair Leslie-Hughes authored
Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=44865Signed-off-by:
-
Alistair Leslie-Hughes authored
Signed-off-by:
-
Alistair Leslie-Hughes authored
Signed-off-by:
-
- 23 Jun, 2020 4 commits
-
-
Rémi Bernon authored
When RIM_EXINPUTSINK is used, messages are received in background only if the foreground process didn't register for rawinput messages itself. Signed-off-by:
-
Rémi Bernon authored
Rawinput messages are not received anymore if the foreground window is from another process. Using RIDEV_INPUTSINK makes it possible to receive them again, but with RIM_INPUTSINK flag. When multiple processes register for rawinput messages, the foreground process will receive the message, as well as any other that registerd with RIM_INPUTSINK flag, including when the foreground process itself did. Currently the messages may be received correctly, but that depends on where the input events are generated, so add another test case with messages sent from the test process, and validate that nothing should be received. Signed-off-by:
-
Rémi Bernon authored
The rawinput messages are received on the target window if is from the same process as the foreground window, it doesn't need to be the foreground window itself, or use RIDEV_INPUTSINK. Signed-off-by:
-
Rémi Bernon authored
This tests basic functionality by injecting mouse event and checking the number of each messages received. Signed-off-by:
-
