RE: [GD-Windows] WA_CLICKACTIVE vs. WM_MOUSEACTIVATE

[Matt D. <ma...@co...>]

It's important to note that Windows' makes a huge distinction between client
and non-client areas of the window and has mutually exclusive messages to
deal with the two areas.  I know I keep forgetting about WM_NCxxx messages
:-(


Matt Davies
Programmer, Confounding Factor
ma...@co...
www.confounding-factor.com



-----Original Message-----
From: gam...@li...
[mailto:gam...@li...]On Behalf Of
Brian Hook
Sent: 30 January 2002 01:33
To: gam...@li...
Subject: RE: [GD-Windows] WA_CLICKACTIVE vs. WM_MOUSEACTIVATE


> 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


_______________________________________________
Gamedevlists-windows mailing list
Gam...@li...
https://lists.sourceforge.net/lists/listinfo/gamedevlists-windows