Path: utzoo!utgpu!watserv1!watmath!att!att!pacbell.com!ucsd!usc!jarthur!hsv3.UUCP
From: jls@hsv3.UUCP (James Seidman)
Newsgroups: comp.windows.ms.programmer
Subject: Re: Tracking the mouse...
Message-ID: <9474@jarthur.Claremont.EDU>
Date: 1 Nov 90 04:37:17 GMT
References: <5538@hsv3.UUCP> <823@tuura.UUCP>
Sender: jseidman@jarthur.Claremont.EDU
Reply-To: jls@hsv3.UUCP
Organization: Headland Technology, Fremont, CA
Lines: 16

risto@tuura.UUCP (Risto Lankinen) writes:
>You could try polling the mouse with GetCursorPos() within the application's
>message loop, and check whether the cursor is inside the desired child window
>by calling WindowFromPoint() .  If it were, you could act directly, or, more
>elegantly, send that window a self-defined WM_USER message with wParam set to
>indicate cursor entering / exiting status when the hWnd returned by Window-
>FromPoint() has changed.

I'm already doing something of the sort in the parent on WM_MOUSEMOVE,
WM_SETCURSOR, and WM_KILLFOCUS.  But none of these help when the user
moves the mouse outside of the parent window fast enough that no messages
get generated in the parent area outside of the child window.

Now, I could use a timer to poll periodically, but this seems like a
terribly inelegant solution.  I was hoping that there would be something
a little nicer to solve the problem (but I'm rapidly losing hope...)