listview
Ulrich Czekalla
ulrich.czekalla at utoronto.ca
Fri Sep 3 11:01:02 CDT 2004
Ok, I'll do some more research and see if I can come up with a better
solution.
Thanks,
/Ulrich
On Fri, Sep 03, 2004 at 12:44:01PM +0200, Rein Klazes wrote:
> On Thu, 2 Sep 2004 17:28:31 -0400, you wrote:
>
> > ChangeLog:
> > Ulrich Czekalla <ulrich at codeweavers.com>
> > Handle WM_BUTTONDOWN operations before dragging test
> > Don't eat WM_LBUTTONUP message
> >
> > Index: dlls/comctl32/listview.c
> > ===================================================================
> > RCS file: /home/wine/wine/dlls/comctl32/listview.c,v
> > retrieving revision 1.393
> > diff -u -r1.393 listview.c
> > --- dlls/comctl32/listview.c 25 Aug 2004 17:33:01 -0000 1.393
> > +++ dlls/comctl32/listview.c 2 Sep 2004 21:21:32 -0000
> > @@ -7927,6 +7927,7 @@
> > else if (msg.message >= WM_LBUTTONDOWN &&
> > msg.message <= WM_RBUTTONDBLCLK)
> > {
> > + DispatchMessageW(&msg);
> > break;
> > }
>
> This was discussed before. The problem here is that Windows/native
> comctl32 *does* eat the WM_LBUTTONUP message ending the mouse track.
>
> The reason why you miss the WM_LBUTTONUP message is that mouse tracking
> is started wrongly under Wine.
>
> Rein.
> --
> Rein Klazes
> rklazes at xs4all.nl
>
More information about the wine-devel
mailing list