From: Alexander Huntley <huntley.alexander@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 50269@debbugs.gnu.org
Subject: bug#50269: 27.2; Request: use GTK continuous scroll events for smooth touchpad scrolling
Date: Mon, 30 Aug 2021 22:26:45 +0100 [thread overview]
Message-ID: <1df288ac-476b-eee0-88bf-482736ac0823@gmail.com> (raw)
In-Reply-To: <837dg2kanc.fsf@gnu.org>
> We are probably having communication difficulties due to terminology
> you are using. pixel-scroll-mode doesn't work on line granularity, it
> actually shifts the display one pixel at a time. If you scroll by
> enough pixels so that the sum total of those pixels amounts to one
> line, pixel-scroll-mode resets the display shift offset to zero and
> scrolls the display by one full line, then it keeps shifting one pixel
> at a time.
>
> Given this description of how pixel-scroll-mode works, what exactly
> would you like to change?
>
> Or maybe looking at this from a different angle: how does the behavior
> you'd like to see differ from what pixel-scroll-mode produces?
pixel-scroll-mode may shift the display one pixel at a time, but it
also "snaps" the display to certain larger intervals, (integer numbers
of lines).
This snapping makes the scrolling jerkier than it needs to be on
touchpads.
If we could use the more precise/frequent data actually coming from
the touchpad, then the user could control the scrolling more precisely:
instead of scrolling by n lines, the user could scroll by as little
as a single pixel at a time.
next prev parent reply other threads:[~2021-08-30 21:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-30 13:35 bug#50269: 27.2; Request: use GTK continuous scroll events for smooth touchpad scrolling Alexander Huntley
2021-08-30 15:57 ` Eli Zaretskii
2021-08-30 18:37 ` Alexander Huntley
2021-08-30 18:40 ` Eli Zaretskii
2021-08-30 19:02 ` Alexander Huntley
2021-08-30 19:14 ` Eli Zaretskii
2021-08-30 21:26 ` Alexander Huntley [this message]
2021-08-31 12:17 ` Eli Zaretskii
2021-08-31 16:33 ` Kévin Le Gouguec
2021-08-31 16:39 ` Eli Zaretskii
2021-09-01 12:57 ` Alexander Huntley
2021-09-01 13:49 ` Eli Zaretskii
2021-08-30 19:28 ` Alan Third
2021-08-30 21:36 ` Alexander Huntley
2021-08-30 22:22 ` Alan Third
2022-08-22 16:03 ` Lars Ingebrigtsen
2022-09-19 19:21 ` Lars Ingebrigtsen
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=1df288ac-476b-eee0-88bf-482736ac0823@gmail.com \
--to=huntley.alexander@gmail.com \
--cc=50269@debbugs.gnu.org \
--cc=eliz@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 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).