Path: utzoo!utgpu!watserv1!watmath!att!att!linac!pacific.mps.ohio-state.edu!zaphod.mps.ohio-state.edu!usc!elroy.jpl.nasa.gov!jarthur!jseidman
From: jseidman@jarthur.Claremont.EDU (James Seidman)
Newsgroups: comp.windows.ms.programmer
Subject: Re: Tracking the mouse...
Message-ID: <9528@jarthur.Claremont.EDU>
Date: 5 Nov 90 04:12:16 GMT
References: <5538@hsv3.UUCP> <823@tuura.UUCP> <58753@microsoft.UUCP>
Reply-To: jls@hsv3.UUCP
Organization: Headland Technology, Fremont, CA
Lines: 20

davidds@microsoft.UUCP (David D'SOUZA) writes:
>In article <823@tuura.UUCP> risto@tuura.UUCP (Risto Lankinen) writes:
>Seems to me that whenever your child window gets the WM_MOUSEMOVE
>message you could capture the mouse (using SetCapture(hwndchild)). 
>This would cause all mouse messages to go to your window regardless of
>where the mouse is.  Now, when the mouse moves outside your window
>rectangle, you simply release the capture.

I thought of this too, and actually tried it.  The problem is that then,
whenever the cursor is inside my child window, the user can't switch away
from it using the normal magic keys (alt-enter, control-escape, etc.).
While this is acceptable for the usual uses of SetCapture (which usually
involve the user making a selection, having a mouse button down, or the
like), it's really unacceptable here.

-- 
Jim Seidman, Headland Technology, 46221 Landing Parkway, Fremont CA 94538
The Doctor: It was a terrible babble of inhuman voices.
Prof. Chronotis: Oh, that was just the undergraduates!
							- Doctor Who, "Shada"