unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: storm@cua.dk (Kim F. Storm)
Cc: Michael Welsh Duggan <md5i@cs.cmu.edu>
Subject: Re: Subject: w32 mouse wheel handling
Date: 26 May 2003 01:22:09 +0200	[thread overview]
Message-ID: <5xel2m7gta.fsf@kfs2.cua.dk> (raw)
In-Reply-To: <200305251519.h4PFJr5C014545@rum.cs.yale.edu>

"Stefan Monnier" <monnier+gnu/emacs@rum.cs.yale.edu> writes:

> I agree on the principle, but I think using mouse-4 and mouse-5 is
> not correct.  It's just an X11 hack.  I'd rather create new events
> like wheel-up and wheel-down and then have a function-key-map to
> translate mouse-4 and mouse-5 to wheel-up and wheel-down (on X).

I agree 100%, that we should not use the mouse-4 and mouse-5 names.  

But I'm less certain about the names for the wheel events though.

I think the wheel-up and wheel-down names are a bit confusing when
compated to existing mouse events like down-mouse-1 and up-mouse-2.

Also, if you look at a typical mouse wheel, it has two directions:
"upwards" (turn the wheel away from yourself) and "downwards" (turn
the wheel towards yourself).  So in the "human context", these should
then correspond to the events wheel-up and wheel-down.  

But inside emacs, the event which scrolls the mouse "away from you"
would be bound to scroll-down and "towards you" to scroll-up, so in
the "emacs context" we could just as well justify to assign the
wheel-up and wheel-down events in the "opposite direction".

So "wheel-up" and "wheel-down" are not really unambiguous.

Furthermore, I have seen mice with two scroll wheels, some of these
have two up/down wheels, others have both up/down and left/right
wheels, and I think our naming of wheel events should be prepared for
this.

So maybe we could simply use names like wheel-1, wheel-2 (first mouse
wheel), mouse-3, mouse-4 (second mouse wheel), etc.

Or we could have wheel-forward-1, wheel-backward-1, etc.

Or wheel+1, wheel-1, wheel+2, wheel-2, etc.

-- 
Kim F. Storm <storm@cua.dk> http://www.cua.dk

  reply	other threads:[~2003-05-25 23:22 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-23 14:47 Subject: w32 mouse wheel handling David PONCE
2003-05-25  4:17 ` Michael Welsh Duggan
2003-05-25  8:34   ` David Ponce
2003-05-25 15:19   ` Stefan Monnier
2003-05-25 23:22     ` Kim F. Storm [this message]
2003-05-26  5:09       ` Kai Großjohann
2003-05-27 12:44         ` Richard Stallman
2003-05-28 22:18           ` David Ponce
2003-05-29  7:33             ` Jason Rumney
2003-05-30  0:50             ` Richard Stallman
2003-05-30 12:14               ` David Ponce
2003-05-26 13:30   ` Jason Rumney
2003-05-27  7:21 ` Jason Rumney
  -- strict thread matches above, loose matches on Subject: below --
2003-05-27  8:12 David PONCE
2003-05-27  8:29 ` Juanma Barranquero
2003-05-27  8:45   ` Jason Rumney
2003-05-27  8:49     ` Juanma Barranquero
2003-05-27 22:41     ` Richard Stallman
2003-05-28  7:50       ` Oliver Scholz
2003-05-27 14:28   ` Stefan Monnier

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=5xel2m7gta.fsf@kfs2.cua.dk \
    --to=storm@cua.dk \
    --cc=md5i@cs.cmu.edu \
    /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).