Re: user32[2/3]: send a WM_MOUSELEAVE even if another window calls TrackMouseEvent before the timer proc is called

[Alexandre Julliard]

Mikołaj Zalewski <mikolaj(a)zalewski.pl> writes:
> @@ -949,6 +954,12 @@ TrackMouseEvent (TRACKMOUSEEVENT *ptme)
>              }
>          }
>      } else {
> +        /* In our implementation it's possible that another window will receive a
> +         * WM_MOUSEMOVE and call TrackMouseEvent before TrackMouseEventProc is
> +         * called. In such a situation post the WM_MOUSELEAVE now */
> +        if (tracking_info.tme.hwndTrack != NULL)
> +            check_mouse_leave(hwnd, hittest);
> +

Shouldn't you check for TME_LEAVE first?

-- 
Alexandre Julliard
julliard(a)winehq.org

user32[2/3]: send a WM_MOUSELEAVE even if another window calls TrackMouseEvent before the timer proc is called

[Mikołaj Zalewski]

Alexandre Julliard wrote:
> Mikołaj Zalewski <mikolaj(a)zalewski.pl> writes:
> > @@ -949,6 +954,12 @@ TrackMouseEvent (TRACKMOUSEEVENT *ptme)
> >             }
> >         }
> >     } else {
> > +        /* In our implementation it's possible that another window will receive a
> > +         * WM_MOUSEMOVE and call TrackMouseEvent before TrackMouseEventProc is
> > +         * called. In such a situation post the WM_MOUSELEAVE now */
> > +        if (tracking_info.tme.hwndTrack != NULL)
> > +            check_mouse_leave(hwnd, hittest);
> > +
>
> Shouldn't you check for TME_LEAVE first?

Yes, we should. I'll send a corrected version.

Mikolaj Zalewski