Re: Missing WM_CAPTURECHANGED message

[Dmitry Timoshkov]

Christopher Thielen  wrote:
> The crux of the bug fix is that calling SetCapture() twice in a row 
> passing your own HWND both times should result in a WM_CAPTURECHANGED 
> message in which the lParam == your HWND. Below is my attempt at writing 
> a test for that but the test never receives the WM_CAPTURECHANGED message.

Message loop can see only posted messages, sent messages go directly
to the message handling procedure. Please add a message test instead
(tests/msg.c).