Re: win32lib: mouse event
- Posted by Derek Parnell <ddparnell at bigpond.com> Mar 25, 2003
- 369 views
On Tue, 25 Mar 2003 11:18:41 +1030, <daryl_vdb at hotmail.com> wrote: [snip] > Well, click is a seperate event anyway, so we don't need to worry about > that. > > Sending the double click event after the mouse is released would be > inconsistant with normal windows behaviour, which is typically the double > click is sent when the mouse is pressed. > > Anyway, after thinking about this, I'm not sure that it ould be a good > idea to include the second WM_LBUTTONDOWN. There would be times you want > to distinguish between a normal click and a double click. If you don't, > it is easy to work around by just treating all LeftDoubleClick events as > LeftDown. But if a LeftDown was sent before a LeftDoubleClick, it would > not be easy to tell whether this LeftDown was a double click or not. So, in summary, win32lib does not have to change, right? -- cheers, Derek Parnell