Re: [GD-Windows] WA_CLICKACTIVE vs. WM_MOUSEACTIVATE

[Andrew G. <an...@ra...>]

I guess you have something like ShowCursor(FALSE); in your program to hide
the system cursor so you can draw your own? 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.

// andrew


----- Original Message -----
From: "Brian Hook" <bri...@py...>
To: <gam...@li...>
Sent: Wednesday, January 30, 2002 1:03 AM
Subject: RE: [GD-Windows] WA_CLICKACTIVE vs. WM_MOUSEACTIVATE


> > Do you ever call SetCapture() to capture the mouse?
>
> Yes.
>
> > And if yes, do you call ReleaseCapture() on deactivate?
>
> Yes.
>
> This might be related to the overall problem, however, so I'll look into
> that.  Right now I'm capturing the mouse on WM_MOUSEMOVE also, although
> I don't remember why =)  Basically, if I get a WM_MOUSEMOVE and the
> point is in the client area, then I do a SetCapture().  If I comment
> this line out, the cursor disappears in the title bar (it's user draw in
> the client area and system draw outside the window, but in the titlebar
> nothing happens).
>
> I would love to be able to get rid of my calls to SetCapture() though.
>
> Brian
>
>
> _______________________________________________
> Gamedevlists-windows mailing list
> Gam...@li...
> https://lists.sourceforge.net/lists/listinfo/gamedevlists-windows
>