From: "Drew Adams" <drew.adams@oracle.com>
To: "'Jason Rumney'" <jasonr@gnu.org>,
"'Chong Yidong'" <cyd@stupidchicken.com>
Cc: emacs-devel@gnu.org
Subject: RE: Why the `click' modifier for a mouse-wheel event?
Date: Sun, 5 Jul 2009 23:40:34 -0700 [thread overview]
Message-ID: <EEDE3EA6FD4C45B5A91F1F90FAD3B0EA@us.oracle.com> (raw)
In-Reply-To: <4A516F3E.6060603@gnu.org>
> >> In Emacs 22 (and 21, 20...), using the mouse wheel did not
> >> add any modifiers to the event that was read. In Emacs 23,
> >> `event-modifiers' for a `mouse-wheel-down-event' or
> >> `mouse-wheel-up-event' returns `(click)'.
> >
> > I think this change was made to make Windows behave like the other
> > ports. IIRC, this was in response to a bug report by Lennart (?),
> > but I can't find it in the tracker right now.
>
> It was bug#687, about wheel events triggering mouse-avoidance, since
> they were not considered as mouse events.
Thanks for tracking that other bug down, Jason. But I don't understand why that
fix to bug #687 is TRT. It seems to me very wrong that a wheel event that does
not in any way involve the user pressing the wheel as a middle mouse button
should be treated as a mouse-button `click' event. I don't understand everything
about bug #687 (and it sounds, from reading it, like others might not either),
but this fix seems off-base.
And I was obviously wrong in my own last post in that bug thread, when I said
that I thought I would not need to change my own code because of your change. As
I mentioned earlier, that change complicates user code - see the examples I
gave. The test for a keyboard-only modifier (shift, control, meta, alt, hyper,
or super) has become downright silly - but perhaps there is a better way to do
it than what I posted?
[OT - BTW, do others find the Emacs bug-maintenance site usable? I found no
field for entering a bug number (e.g. 687), to show a specific bug, so I
searched the page for it. Not finding it, I tried to show the Archived bugs
(there is a field for that, at least). More than 50 minutes later (!), with
still no page displayed, I gave up, just clicked some other bug link, and
changed the bug number in the resulting URL. I can't believe this is the best
bug-maintenance tool we could find, but so be it.]
next prev parent reply other threads:[~2009-07-06 6:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-26 17:15 Why the `click' modifier for a mouse-wheel event? Drew Adams
2009-06-26 17:26 ` Drew Adams
2009-06-26 19:32 ` Chong Yidong
2009-07-06 3:27 ` Jason Rumney
2009-07-06 6:40 ` Drew Adams [this message]
2009-07-06 8:31 ` Jan D.
2009-07-06 15:34 ` Emacs bug list [was: Why the `click' modifier for a mouse-wheel event?] Drew Adams
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=EEDE3EA6FD4C45B5A91F1F90FAD3B0EA@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=cyd@stupidchicken.com \
--cc=emacs-devel@gnu.org \
--cc=jasonr@gnu.org \
/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.