| commit | f068e329c1fe45a6a55c7a3ea013740dbb4f41db | |
| author | Ken Thomases <ken@codeweavers.com> | |
| Wed, 11 Dec 2013 18:50:55 +0000 (11 12:50 -0600) | ||
| committer | Alexandre Julliard <julliard@winehq.org> | |
| Thu, 12 Dec 2013 11:06:47 +0000 (12 12:06 +0100) | ||
| tree | 7c623e7db05801b28836019db5d8a59789eaed65 | treesnapshot (tar.gz zip) |
| parent | b3cc34e5b0a3e40288e7b9888773dc6aeb6dd37d | commitdiff |
winemac: Send WM_{ENTER, EXIT}SIZEMOVE before/after window dragging and run an internal event loop during.
This simulates some of what would happen if user32 were managing the drag. The
click in the caption would cause WM_SYSCOMMAND/SC_MOVE. The processing of that
message is synchronous and doesn't return until the move is complete.
Some games require that "blocking" in the internal event loop to prevent them
from misbehaving during the drag.
This simulates some of what would happen if user32 were managing the drag. The
click in the caption would cause WM_SYSCOMMAND/SC_MOVE. The processing of that
message is synchronous and doesn't return until the move is complete.
Some games require that "blocking" in the internal event loop to prevent them
from misbehaving during the drag.