From: "Drew Adams" <drew.adams@oracle.com>
To: "'Stefan Monnier'" <monnier@iro.umontreal.ca>
Cc: 7802@debbugs.gnu.org
Subject: bug#7802: bug #7802: 24.0.50; Extraneous `mouse-3' event when do `double-mouse-3'
Date: Fri, 7 Jan 2011 22:36:04 -0800 [thread overview]
Message-ID: <9496EDBB00F3470E9417340D3CDBA5E1@us.oracle.com> (raw)
In-Reply-To: <jwvhbdk2dmo.fsf-monnier+emacs@gnu.org>
> > Sounds to me like this "design" is just a side effect of
> > the implementation.
>
> That might be the case. There is a "design" argument in favor of this
> behavior, tho, which is that otherwise we'd have to wait after a click
> before running its command, to check whether it was the first part of
> a double-click or not.
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?
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.
> Of course, we could try and only perform this waiting in the
> case where there is a double-click binding, thus minimizing such
> undesirable delays, but it still might lead to undesirable delays
> giving the impression the system is somewhat unresponsive.
unresponsive...or just smart, correctly sensitive to what the user did.
I suppose your proposed optimization might make sense, if it doesn't lead to any
problems of its own.
But why not just try to wait and see what the user action really is? How do we
know that would make things seem unresponsive? Again, I cannot imagine that a
system could short-circuit things the way Emacs apparently does and still be
trustworthy.
I repeat that I know nothing about how such things are handled usually, but what
Emacs does just seems wrong (flawed) to me. Does it sound right to you? What
am I missing? (Probably a lot.)
> PS: Of course, the same holds for double-vs-triple clicks, tho it's
> largely irrelevant.
Triple-clicks are no doubt rarer, if that's what you mean. But I wouldn't want
to have double-click confirm "Do you really want to vote for Ronald McDonald?"
and have triple-click confirm "Do you really want to launch this missile and
start WW3?" The way it is designed now nothing important can be allowed to be
disambiguated by the click count, it seems. ;-)
next prev parent reply other threads:[~2011-01-08 6:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-07 19:11 bug#7802: 24.0.50; Extraneous `mouse-3' event when do `double-mouse-3' Drew Adams
2011-01-07 19:20 ` bug#7802: bug #7802: " Drew Adams
2011-01-07 19:38 ` Drew Adams
2011-01-08 5:03 ` Stefan Monnier
2011-01-08 6:36 ` Drew Adams [this message]
2011-01-08 16:01 ` Jason Rumney
2011-01-08 17:22 ` Drew Adams
2011-01-09 3:34 ` Jason Rumney
2011-01-09 14:18 ` Drew Adams
2011-01-13 5:35 ` Chong Yidong
2011-01-13 7:15 ` Drew Adams
2011-01-15 3:29 ` Chong Yidong
2011-08-08 18:45 ` Drew Adams
2011-08-08 20:52 ` Chong Yidong
2011-01-13 17:32 ` Stefan Monnier
2011-01-08 19:50 ` grischka
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9496EDBB00F3470E9417340D3CDBA5E1@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=7802@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).