GNU bug report logs -
#7802
24.0.50; Extraneous `mouse-3' event when do `double-mouse-3'
Previous Next
Full log
View this message in rfc822 format
"Drew Adams" <drew.adams <at> oracle.com> writes:
> I'm no expert on these things, but isn't that what the system (whatever system
> is handling mouse events) needs to do anyway? Doesn't Windows, for instance,
> have to wait to see whether an event is a single-click, double-click, or
> triple-click?
No. Windows does the same as Emacs, which is why we inherit this
behaviour.
> I can't see how it could be otherwise (logically). I can't imagine
> some action kicking in just as soon as the first click is detected,
> without waiting to see whether the _user_ action is actually a single
> click or is really a double click.
The standard situation on Windows is rather more limited. There are no
double click bindings for mouse-2 or mouse-3 in most programs or on the
desktop, only for mouse-1. And the click event for mouse-1 generally
selects the item below the mouse pointer, which the double click event
then uses.
> But why not just try to wait and see what the user action really is?
How long do you propose to wait?
This bug report was last modified 13 years and 312 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.