From: Jason Rumney <jasonr@gnu.org>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: 7802@debbugs.gnu.org
Subject: bug#7802: bug #7802: 24.0.50; Extraneous `mouse-3' event when do `double-mouse-3'
Date: Sun, 09 Jan 2011 00:01:05 +0800 [thread overview]
Message-ID: <87tyhje666.fsf@gnu.org> (raw)
In-Reply-To: <9496EDBB00F3470E9417340D3CDBA5E1@us.oracle.com> (Drew Adams's message of "Fri, 7 Jan 2011 22:36:04 -0800")
"Drew Adams" <drew.adams@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?
next prev parent reply other threads:[~2011-01-08 16:01 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
2011-01-08 16:01 ` Jason Rumney [this message]
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=87tyhje666.fsf@gnu.org \
--to=jasonr@gnu.org \
--cc=7802@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
/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).