unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Heerdegen <michael_heerdegen@web.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 61307@debbugs.gnu.org
Subject: bug#61307: 30.0.50; pixel-scroll-precision-mode: window-scroll-functions?
Date: Wed, 15 Feb 2023 05:06:12 +0100	[thread overview]
Message-ID: <87sff7374b.fsf@web.de> (raw)
In-Reply-To: <83edqse6qr.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 14 Feb 2023 15:06:36 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

> > I don't see the hook called for each pixel.  What do you mean?
>
> Each time you do the smallest possible scroll, by how many pixels, or
> by what fraction of the screen-line's height does Emacs scroll the
> window?  IOW, by how many pixels is the display scrolled for each call
> to window-scroll-functions?
>
> Precision pixel-scrolling supports many different devices (mice and
> touch-pads), which can scroll at very different resolutions.  The
> possibility that window-scroll-functions be called too frequently
> depends on what exactly do your device and your Emacs build support in
> this scenario, and I don't yet have a clear idea about that, since you
> didn't tell.

I feel a bit lost.  What should I tell?  I have no idea what I could
know about this that you don't already know.

But I understand that what I see when scrolling with a normal wheel
mouse is only one case we need to handle.  AFAIU, scrolling by
dragging the vertical scroll bar is not handled by precision scrolling.

So we speak about touch events (although
`pixel-scroll-precision-mode-map' only binds <touch-end>, but that event
may also be generated very often) and mice with a more or less
continuous scroll wheel (or ball) and such things.

I don't have access to such a device and really feel uncomfortable to
suggest a patch for these cases I must admit.

Or would you suggest to call the window-scroll functions just after a
certain time limit?  A pixel-delta limit would probably not be
sufficient, since we want to call the functions also for small scroll
amounts if they are not directly followed by another scroll (I guess).

So do we just want to use a timer for this?  Or use a combination of
those approaches (scrolling farther than a certain amount fires the
scroll functions immediately, but also small amounts call them if the
user doesn't scroll after delta more milliseconds)?


Michael.





  reply	other threads:[~2023-02-15  4:06 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-06  1:49 bug#61307: 30.0.50; pixel-scroll-precision-mode: window-scroll-functions? Michael Heerdegen
2023-02-06 12:15 ` Eli Zaretskii
2023-02-06 21:30   ` Michael Heerdegen
2023-02-12 12:15     ` Eli Zaretskii
2023-02-13  2:20       ` Michael Heerdegen
2023-02-13  3:31         ` Eli Zaretskii
2023-02-13  3:44           ` Michael Heerdegen
2023-02-13 12:56             ` Eli Zaretskii
2023-02-14  1:30               ` Michael Heerdegen
2023-02-14 13:06                 ` Eli Zaretskii
2023-02-15  4:06                   ` Michael Heerdegen [this message]
2023-02-15 13:21                     ` Eli Zaretskii
2023-02-16  4:57                       ` Michael Heerdegen
2023-02-16  8:22                         ` Eli Zaretskii
2023-02-16  8:47                           ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-16  8:54                           ` Michael Heerdegen
2023-02-19  5:50                           ` Michael Heerdegen
2023-02-19  6:54                             ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-19  7:36                               ` Michael Heerdegen
2023-02-19  8:30                                 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-06 14:07 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-06 15:25   ` 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

  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=87sff7374b.fsf@web.de \
    --to=michael_heerdegen@web.de \
    --cc=61307@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).