From: Alan Third <alan@idiocy.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 35389@debbugs.gnu.org, rpluim@gmail.com, npostavs@gmail.com
Subject: bug#35389: 27.0.50; [PATCH] Emacs on macOS sets mouse-wheel variables directly
Date: Sun, 19 May 2019 13:41:04 +0100 [thread overview]
Message-ID: <20190519124104.GB4246@breton.holly.idiocy.org> (raw)
In-Reply-To: <83pnonbuyl.fsf@gnu.org>
On Sun, May 12, 2019 at 05:36:50PM +0300, Eli Zaretskii wrote:
> > Date: Sun, 12 May 2019 12:05:04 +0100
> > From: Alan Third <alan@idiocy.org>
> > Cc: rpluim@gmail.com, 35389@debbugs.gnu.org, npostavs@gmail.com
> >
> > Unfortunately we can’t just treat each of these NSEvents as a request
> > to scroll a single line as we can receive many small requests very
> > quickly. This is what Emacs used to do and it was basically useless.
> > The slightest two finger drag on the trackpad could result in Emacs
> > scrolling several pages.
> >
> > What the current code does is add those pixel values up until they
> > reach a certain value, then send Emacs an event telling it to scroll.
> > Unfortunately those pixel values include a built‐in acceleration
> > factor, so the more the user drags their fingers across the trackpad,
> > the higher the pixel values will be, proportionally. We can’t disable
> > that, and as far as I can tell the user can’t even disable it for the
> > whole system.
>
> Is the algorithm used by the system to "accelerate" known? If so,
> could we "un-accelerate" those values, by scaling them back to the
> original amount of dragging received from the user, as if acceleration
> was disabled? Then we could apply our own acceleration as on other
> platforms. Would that work?
I don’t think there’s a published algorithm. Generally Apple would
rather we all conform than do our own thing. After some thought I’ve
remembered that it’s possible to pick up the touch events at a lower
level, so it may be possible to do a comparison and try to reverse
engineer it. Or just bypass their scrolling completely. I’m not sure
how practical that would be though.
I hope your other questions were answered in the discussion with Tak,
so I won’t retread that ground here.
--
Alan Third
next prev parent reply other threads:[~2019-05-19 12:41 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-23 9:47 bug#35389: 27.0.50; [PATCH] Emacs on macOS sets mouse-wheel variables directly Robert Pluim
2019-04-23 11:17 ` Noam Postavsky
2019-04-23 11:38 ` Robert Pluim
2019-05-10 15:29 ` Robert Pluim
2019-05-10 19:53 ` Eli Zaretskii
2019-05-10 21:25 ` Alan Third
2019-05-11 6:12 ` Eli Zaretskii
2019-05-11 9:54 ` Robert Pluim
2019-05-11 10:58 ` Eli Zaretskii
2019-05-11 22:50 ` Alan Third
2019-05-12 4:58 ` Eli Zaretskii
2019-05-12 11:05 ` Alan Third
2019-05-12 14:36 ` Eli Zaretskii
2019-05-19 12:41 ` Alan Third [this message]
2019-05-12 23:29 ` Tak Kunihiro
2019-05-13 14:26 ` Eli Zaretskii
2019-05-16 9:00 ` Tak Kunihiro
2019-05-16 13:55 ` Eli Zaretskii
2019-05-16 23:24 ` Tak Kunihiro
2019-05-17 5:39 ` Eli Zaretskii
2019-05-18 8:50 ` Tak Kunihiro
2019-05-18 9:16 ` Eli Zaretskii
2019-05-19 12:32 ` Alan Third
2019-05-22 6:22 ` Eli Zaretskii
2019-05-23 4:24 ` Tak Kunihiro
2019-05-23 4:55 ` Eli Zaretskii
2019-06-06 2:21 ` Tak Kunihiro
2019-06-07 18:31 ` Alan Third
2020-08-10 11:32 ` Lars Ingebrigtsen
2020-08-10 13:04 ` Robert Pluim
2020-08-10 13:19 ` Lars Ingebrigtsen
2019-05-11 22:53 ` Alan Third
2019-05-11 23:06 ` Alan Third
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=20190519124104.GB4246@breton.holly.idiocy.org \
--to=alan@idiocy.org \
--cc=35389@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=npostavs@gmail.com \
--cc=rpluim@gmail.com \
/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).