Re: MouseDown causes MouseLeave NOT to be fired. by discussion
discussion
Wed Nov 26 09:00:13 CST 2003
Workaround for MS's lack of MouseLeave event is to detrect the MouseMove
coordinates and if they are larger than the control or negative, fire the
MouseLeave event youreself if MS dont do it.
Will this be fired in later versions because I dont like having cludge code
in there to workaround lack of features.
<discussion@discussion.microsoft.com> wrote in message
news:uDvjNqCtDHA.1744@TK2MSFTNGP12.phx.gbl...
> I do. For example, say I have a mouse down, and changed the cursor, I
move
> outside with teh mouse still down, how can I know when to change the
cursor
> again to indicate its OUTSIDE the region of my control.
>
> With the current messging model I cannot. I would need to get a
MouseLeave
> event even with MouseDown to detect that.
>
>
>
> "Phil Da Lick!" <phil_the_lick@nospam.hotmail.com> wrote in message
> news:esAU3ZCtDHA.3416@tk2msftngp13.phx.gbl...
> > <discussion@discussion.microsoft.com> wrote in message
> > news:uRRt$%23BtDHA.2932@TK2MSFTNGP11.phx.gbl...
> > > To repro.
> > >
> > > Keep the mouse down and drag out of control, no mouse leave event
> ever.
> > >
> > > BUG BUG BUG :P
> >
> > I dont think so. Not knowing the framework at all, I'n guessing that
this
> is
> > caused by the framework capturing the mouse during mouse down. If the
> mouse
> > is captured, you wont get a mouse leave at all, as the system fires
> > wm_mousemove messages at the window even if the cursor is outside the
> client
> > area.
> >
> >
>
>