| commit | ababea0fd7036ab13ec17d31afbd584c39f62696 | |
| author | Dmitry Timoshkov <dmitry@baikal.ru> | |
| Mon, 25 Oct 2021 09:41:59 +0000 (25 12:41 +0300) | ||
| committer | Alexandre Julliard <julliard@winehq.org> | |
| Mon, 25 Oct 2021 21:05:47 +0000 (25 23:05 +0200) | ||
| tree | 6d7b2706dbe3b5eec2d17b066bee8a86d3be9b6c | treesnapshot (tar.gz zip) |
| parent | 35532015cba9c2bb08d1b50df2dc45b0d6a18d5e | commitdiff |
user32: DragDetect() should enter its message loop only if the left mouse button is pressed.
There's an application that calls DragDetect() on every WM_MOUSEMOVE
message, and this breaks handling of mouse events. A simple test app
shows that on Windows DragDetect() starts its message loop when left
mouse button is pressed.
Signed-off-by: Dmitry Timoshkov <dmitry@baikal.ru>
Signed-off-by: Alexandre Julliard <julliard@winehq.org>
There's an application that calls DragDetect() on every WM_MOUSEMOVE
message, and this breaks handling of mouse events. A simple test app
shows that on Windows DragDetect() starts its message loop when left
mouse button is pressed.
Signed-off-by: Dmitry Timoshkov <dmitry@baikal.ru>
Signed-off-by: Alexandre Julliard <julliard@winehq.org>
| dlls/user32/tests/win.c | diffblobblamehistory | |
| dlls/user32/win.c | diffblobblamehistory |