all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: hiroya.ebine1@gmail.com, kzhr@d1.dion.ne.jp, max@mal-richtig.de,
	65070@debbugs.gnu.org
Subject: bug#65070: 29.1; (Only on Windows) Both touchpad scroll gestures scroll the screen up and down.
Date: Sun, 20 Aug 2023 08:19:49 +0800	[thread overview]
Message-ID: <87bkf2efa2.fsf@yahoo.com> (raw)
In-Reply-To: <83350fyvma.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 19 Aug 2023 17:06:37 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

>> Cc: hiroya.ebine1@gmail.com, max@mal-richtig.de, 65070@debbugs.gnu.org
>> Date: Sat, 19 Aug 2023 10:54:34 +0300
>> From: Eli Zaretskii <eliz@gnu.org>
>> 
>> Po Lu, I'd appreciate if you'd take me through the code that produces
>> and uses these wheel events, documented in the ELisp reference manual
>> as (wheel-up/down POSITION CLICKS LINES PIXEL-DELTA).  Specifically:
>> 
>>   . what is the conventions for signs in the data of the PIXEL-DELTA
>>     cons cell?

The pertinent delta is the one for the axis whose value is larger.  If
more scrolling has taken place on the X axis, then the relevant delta is
that for the Y axis.  Otherwise, it is the delta for the Y axis.

If that delta is less than 0, a wheel-down event is produced.
Otherwise, a wheel-up event is produced instead.

>>   . where and how are the PIXEL-DELTA data used for scrolling?

Only in pixel-scroll-precision-mode; the traditional mouse wheel
scrolling code derives the direction in which to scroll from the type of
the wheel event.





  reply	other threads:[~2023-08-20  0:19 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-04 15:32 bug#65070: 29.1; (Only on Windows) Both touchpad scroll gestures scroll the screen up and down Hiroya Ebine
2023-08-05  9:04 ` bug#65070: 29.1; (Only on Windows) Both touchpad scroll gestures scroll the screen up only Hiroya Ebine
2023-08-05 10:44   ` Eli Zaretskii
2023-08-05  9:51 ` bug#65070: 29.1; (Only on Windows) Both touchpad scroll gestures scroll the screen up and down Eli Zaretskii
2023-08-07 13:18   ` Hiroya Ebine
2023-08-07 14:05     ` Eli Zaretskii
2023-08-08 10:19 ` bug#65070: max
2023-08-08 12:46   ` bug#65070: Eli Zaretskii
2023-08-08 12:54     ` bug#65070: Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-08 13:04       ` bug#65070: Eli Zaretskii
2023-08-18 16:49 ` bug#65070: 29.1; (Only on Windows) Both touchpad scroll gestures scroll the screen up and down Kazuhiro Ito
2023-08-18 18:26   ` Eli Zaretskii
2023-08-18 18:39     ` Corwin Brust
2023-08-18 22:58       ` Kazuhiro Ito
2023-08-19  7:56         ` Eli Zaretskii
2023-08-19 13:46           ` Kazuhiro Ito
2023-08-19 14:00             ` Eli Zaretskii
2023-08-18 22:54     ` Kazuhiro Ito
2023-08-19  7:54       ` Eli Zaretskii
2023-08-19 13:45         ` Kazuhiro Ito
2023-08-19 13:58           ` Eli Zaretskii
2023-08-19 15:27             ` Kazuhiro Ito
2023-08-19 15:32               ` Eli Zaretskii
2023-08-20  0:16                 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-20  6:28                   ` Eli Zaretskii
2023-08-20 13:14                     ` Kazuhiro Ito
2023-08-20 13:34                       ` Eli Zaretskii
2023-08-19 14:06         ` Eli Zaretskii
2023-08-20  0:19           ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-08-20  6:34             ` Eli Zaretskii
2023-08-20  7:04               ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-20  7:13                 ` Eli Zaretskii
2023-08-20  7:43                   ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-20  8:10                     ` Eli Zaretskii

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=87bkf2efa2.fsf@yahoo.com \
    --to=bug-gnu-emacs@gnu.org \
    --cc=65070@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=hiroya.ebine1@gmail.com \
    --cc=kzhr@d1.dion.ne.jp \
    --cc=luangruo@yahoo.com \
    --cc=max@mal-richtig.de \
    /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.