From: David Kastrup <dak@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: [PATCH] Let input queue deal gracefully with up-events
Date: Thu, 29 Jan 2015 00:06:10 +0100 [thread overview]
Message-ID: <874mrapkt9.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <jwvbnlimtzo.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Wed, 28 Jan 2015 17:19:15 -0500")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>> - Down-clicks are eliminated.
>> + Up/Down-clicks are eliminated.
>
> Actually, up-clicks (in the sens of *mouse* clicks) are not
> eliminated.
Well, they are at _this_ location. *mouse* clicks have been converted
to click/drag at that point.
> I think it's be better to explain that we auto-eliminate both the
> "down-<foo>" and "up-<foo>" events such that, depending on which of the
> up or down part of an event is the important one, we use "down-<foo> and
> <foo>" or "<foo> and up-<foo>"
Well, it is not really comparable since down-xxx + up-xxx for the mouse
are combined into one xxx or drag-xxx event: in this case the
"eliminated" down-xxx event still has its timing and area data
integrated into the resulting event.
When discarding an up-xxx event, the corresponding xxx event has already
been delivered. I've thought about _modifying_ the original xxx event
to add the up-xxx info, but in the case where you need it, you need
something to trigger the related action anyway, and if such event-fixup
needs to be done, it can be done by the separately bound up-xxx code
under user control rather than silently modifying an already processed
event.
So the xxx-down/xxx combination has to work differently from xxx/xxx-up.
But the point is that this difference is in the keyboard queue
_frontend_ (the one creating the Lisp event, whether natively or
synthetically). The keyboard queue backend can ignore this difference.
--
David Kastrup
next prev parent reply other threads:[~2015-01-28 23:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-28 13:31 [PATCH] Let input queue deal gracefully with up-events David Kastrup
2015-01-28 14:58 ` Alan Mackenzie
2015-01-28 15:19 ` [PATCH v1] " David Kastrup
2015-02-05 17:23 ` David Kastrup
2015-02-05 19:11 ` Stefan Monnier
2015-02-05 19:27 ` David Kastrup
2015-02-05 21:07 ` Ivan Shmakov
2015-02-05 21:42 ` David Kastrup
2015-02-05 19:17 ` Ivan Shmakov
2015-01-28 19:35 ` [PATCH] " Stefan Monnier
2015-01-28 19:50 ` David Kastrup
2015-01-28 22:14 ` Stefan Monnier
2015-01-28 22:55 ` David Kastrup
2015-01-28 22:19 ` Stefan Monnier
2015-01-28 23:06 ` David Kastrup [this message]
2015-01-29 3:57 ` Stefan Monnier
2015-01-29 8:49 ` David Kastrup
2015-01-29 15:00 ` Stefan Monnier
2015-01-29 15:14 ` David Kastrup
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874mrapkt9.fsf@fencepost.gnu.org \
--to=dak@gnu.org \
--cc=emacs-devel@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.