OpenEuphoria

Re: win32lib: mouse event

• Posted by daryl_vdb at hotmail.com Mar 25, 2003
• 379 views

>Though to be nice and logically consistant I suppose we should be seeing 
>...
>  WM_LBUTTONDOWN
>  WM_LBUTTONUP
>  WM_LBUTTONCLK  WM_LBUTTONDOWN
>  WM_LBUTTONUP
>  WM_LBUTTONDBLCLK
>
>However there is no such thing as WM_LBUTTONCLK.

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.

regards,
Daryl Van Den Brink