| commit | df5d632324815549d0e7933e64b1d30265145585 | |
| author | Rémi Bernon <rbernon@codeweavers.com> | |
| Mon, 15 Jun 2020 10:05:42 +0000 (15 12:05 +0200) | ||
| committer | Alexandre Julliard <julliard@winehq.org> | |
| Tue, 23 Jun 2020 20:45:17 +0000 (23 22:45 +0200) | ||
| tree | fc6edfa170523c27d97b657e26da070629073edf | treesnapshot (tar.gz zip) |
| parent | 8c7c0c5504f838253646ac5f47c9be178091de99 | commitdiff |
user32/tests: Add inter-process rawinput message tests.
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 <rbernon@codeweavers.com>
Signed-off-by: Alexandre Julliard <julliard@winehq.org>
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 <rbernon@codeweavers.com>
Signed-off-by: Alexandre Julliard <julliard@winehq.org>
| dlls/user32/tests/input.c | diffblobblamehistory |