RE: [GD-Windows] WA_CLICKACTIVE vs. WM_MOUSEACTIVATE

[Brian H. <bri...@py...>]

> I guess you have something like ShowCursor(FALSE);

Exactly.

> Instead of using SetCapture, why not detect WM_NCMOUSEMOVE 
> messages and make the system cursor visible so that it is 
> displayed in the title bar.

Hey, that works! =) Originally I was using SetCapture() because
WM_MOUSEMOVE wouldn't report movements outside the client area (so I
didn't know when to ShowCursor( TRUE )), not to mention the cursor
wasn't being drawn correctly in the titlebar.

By also trapping WM_NCMOUSEMOVE and doing a ScreenToClient() and posting
that as a regular mousemove to my own event queue, it allowed me to
ditch SetCapture() -- however, since I wasn't sure I was going to be
able to fix all this, I ended up removing my dependency on
WA_CLICKACTIVE =|

Anyway, looks like things are much better structured now.  Less cruft,
that's for sure.  Thanks to everyone that helped!

Brian