RE: [GD-Windows] WA_CLICKACTIVE vs. WM_MOUSEACTIVATE

[Brian S. <bs...@mi...>]

> > This might be related to the overall problem
>=20
> Well, removing SetCapture() allowed me to get those messages.
>=20
> > 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).
>=20
> The above remains a problem -- I can get rid of the calls to
> SetCapture() if I'm willing to live with an invisible cursor on the
> titlebar.  This is rather bothersome since it makes moving the window
> around very difficult.

I think SetCapture is just going to cause you problems...I never had to
use it to write things that ran in a window.

Are you giving your window a cursor in your WNDCLASS (when you call
RegisterClass)?  If you didn't do that, I wouldn't be surprised if you
didn't get a cursor in your non-client area (you know, the hipster term
for the title bar :).  I believe that ShowCursor will still control
cursor visibility in your client area (which is what you want, since
you're drawing your own there), so it shouldn't affect your app.

If that's not it, then it beats the hell outta me!

--brian