https://bugs.freedesktop.org/show_bug.cgi?id=101139
--- Comment #52 from Nate Graham ---
Yep, this is fixed for me. Many thanks for all your hard work, Peter!
--
You are receiving this mail because:
You are the assignee for the bug.___
wayland-bugs ma
https://bugs.freedesktop.org/show_bug.cgi?id=101139
Peter Hutterer changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=101139
--- Comment #50 from Nate Graham ---
Being someone who prefers the macOS touchpad acceleration curve, that patch
radically improves things for my hardware and motion preferences. Bug thumbs up
from me!
--
You are receiving this mail because:
Y
https://bugs.freedesktop.org/show_bug.cgi?id=101139
--- Comment #49 from Peter Hutterer ---
Patch (squashed and polished) is on the list now:
https://lists.freedesktop.org/archives/wayland-devel/2018-May/038172.html
The speed range has significantly increased, so this should cover more
use-cases
https://bugs.freedesktop.org/show_bug.cgi?id=101139
Nate Graham changed:
What|Removed |Added
Status|NEEDINFO|NEW
--- Comment #48 from Nate Graham ---
https://bugs.freedesktop.org/show_bug.cgi?id=101139
--- Comment #47 from Peter Hutterer ---
Ok, another version to test please:
https://github.com/whot/libinput/tree/wip/touchpad-pointer-accel-v6
Still feels roughly like the macOS one though there are some differences that
tbh I can't quite put
https://bugs.freedesktop.org/show_bug.cgi?id=101139
--- Comment #46 from Tim Richardson ---
sorry wrong bug report
--
You are receiving this mail because:
You are the assignee for the bug.___
wayland-bugs mailing list
wayland-bugs@lists.freedesktop.or
https://bugs.freedesktop.org/show_bug.cgi?id=101139
--- Comment #45 from Tim Richardson ---
In 90-libinput-model-quirks.hwdb
the two current rules end with a colon
I don't know the syntax of this file, but there is no other example of this
pattern in the file
when I made a separate P50 rule, I
https://bugs.freedesktop.org/show_bug.cgi?id=101139
--- Comment #44 from Peter Hutterer ---
Created attachment 138716
--> https://bugs.freedesktop.org/attachment.cgi?id=138716&action=edit
synaptics-libinput-comparison.svg
Please keep this bug on-topic, the hysteresis issues are not for this bu
https://bugs.freedesktop.org/show_bug.cgi?id=101139
--- Comment #43 from Nate Graham ---
Still not quite perfect, but definitely better than the status quo! Feels best
for me at around accel value -0.1. I can still feel that jarring hard "jump"
when the acceleration curve changes. And it is still
https://bugs.freedesktop.org/show_bug.cgi?id=101139
--- Comment #42 from Peter Hutterer ---
Awesome, thanks. I hope Nathan can chime in too with some testing comments,
I'll work on getting the range of the acceleration right (or at least big
enough that it should cover most cases). that should, h
https://bugs.freedesktop.org/show_bug.cgi?id=101139
--- Comment #41 from Greg Reichow ---
(In reply to Peter Hutterer from comment #40)
> Can I get you to try a84e79b4aee3563a37485de13c9448981afa4f7c on
> https://github.com/whot/libinput/tree/wip/touchpad-pointer-accel-v5
>
> This one has a more
https://bugs.freedesktop.org/show_bug.cgi?id=101139
Peter Hutterer changed:
What|Removed |Added
Status|NEW |NEEDINFO
--- Comment #40 from Peter Hu
https://bugs.freedesktop.org/show_bug.cgi?id=101139
--- Comment #39 from Peter Hutterer ---
I forgot: to do the above test, #if 0 around gdk_window_set_cursor() in
tools/libinput-debug-gui.c, otherwise the system cursor is not visible.
--
You are receiving this mail because:
You are the assigne
https://bugs.freedesktop.org/show_bug.cgi?id=101139
--- Comment #38 from Peter Hutterer ---
For the archives, I've done a visual comparison to the synaptics driver,
basically by running Xorg with synaptics and libinput debug-gui with libinput
(without the patch above, just git master at a59ce1c)
https://bugs.freedesktop.org/show_bug.cgi?id=101139
--- Comment #37 from Nate Graham ---
I think it's both. If you think about it; they're two sides of the same coin: a
shallower initial acceleration starts to look like a smooth curve the more
segments are added.
Since it's a definite improvemen
https://bugs.freedesktop.org/show_bug.cgi?id=101139
--- Comment #36 from Peter Hutterer ---
The jump is probably caused by the angle between flat and actual acceleration
which still looks like this: _/ (ascii-art! :)
Smoothing this out to be more of a curve may or may not help.
Or the jump is c
https://bugs.freedesktop.org/show_bug.cgi?id=101139
--- Comment #35 from Nate Graham ---
Preliminary impressions: Feels quite nice at 0.0 "libinput accel speed" (i.e
with no configuration). Definitely an improvement over the current profile. It
does still feel like there's an abrupt jump in accel
https://bugs.freedesktop.org/show_bug.cgi?id=101139
--- Comment #34 from Nate Graham ---
Thanks, I'll give that a whirl later today!
--
You are receiving this mail because:
You are the assignee for the bug.___
wayland-bugs mailing list
wayland-bugs@li
https://bugs.freedesktop.org/show_bug.cgi?id=101139
--- Comment #33 from Peter Hutterer ---
Created attachment 138012
--> https://bugs.freedesktop.org/attachment.cgi?id=138012&action=edit
0001-filter-match-accel-roughly-with-macos.patch
This patch matches the macos pointer acceleration, afaict
https://bugs.freedesktop.org/show_bug.cgi?id=101139
--- Comment #32 from Peter Hutterer ---
doh, sorry, hit the wrong button. Continued:
More experimenting with the lowclip patch is needed, and it needs to be
compared to the original touchpad pointer accel (for which I got a lot of
complaints fo
https://bugs.freedesktop.org/show_bug.cgi?id=101139
--- Comment #31 from Peter Hutterer ---
Hooray. The good news: based on these videos, I don't think we have a libinput
*bug*, this does appear to be just a different preference. AFAICT, the movement
matches what I got with the lowclip patch, at
https://bugs.freedesktop.org/show_bug.cgi?id=101139
--- Comment #30 from Greg Reichow ---
See video attached. This was using the lowclip patch I mentioned with accel @
0. For reference, the physical trackpad distance covered in the video is about
90mm in 3 seconds. So roughly 30mm/sec.
I ro
https://bugs.freedesktop.org/show_bug.cgi?id=101139
--- Comment #29 from Peter Hutterer ---
https://github.com/whot/libinput/tree/wip/evemu-v3 is the closest I have so
far. It's still WIP so the output format isn't stable. Run with:
sudo ./build/libinput-record --with-libinput /dev/input/eventX
https://bugs.freedesktop.org/show_bug.cgi?id=101139
--- Comment #28 from Greg Reichow ---
Couple comments to answer above:
1. Not using a Hi-dpi display. Reported resolution is 1680 x 1050.
2. Exact machine is a 2011 MacBook Pro 8,2
3. Agree the earlier patch was too fast. I also found I did
https://bugs.freedesktop.org/show_bug.cgi?id=101139
--- Comment #27 from Nate Graham ---
> [1] having said that, I'm now wondering what's going on there, because if I
move 10mm, it moves by ~10mm on the screen, not 3.7
And that, I think, is exactly the bug we're trying to get to the bottom of.
https://bugs.freedesktop.org/show_bug.cgi?id=101139
--- Comment #26 from Peter Hutterer ---
And here's the thing - libinput's acceleration works in physical distances. So
the hw shouldn't really matter because a speed of 10mm/s is always that,
regardless of the hardware. As long as touchpad-edge-
https://bugs.freedesktop.org/show_bug.cgi?id=101139
--- Comment #25 from Nate Graham ---
Funny, I notice a MASSIVE difference (all Mac touchpads feel the same; there's
no moderl/year difference in touchpad feel). I'm the kind of person who wants a
touchpad so good that I don't feel the urge to us
https://bugs.freedesktop.org/show_bug.cgi?id=101139
--- Comment #24 from Peter Hutterer ---
I do, a 2015 macbook air. And while I admit there are differences, I don't
think they're that big. And that's the biggest puzzle, I can switch between the
air and the t440 and notice a bit of a difference
https://bugs.freedesktop.org/show_bug.cgi?id=101139
Nate Graham changed:
What|Removed |Added
Summary|Acceleration still too slow |Acceleration still too fast
30 matches
Mail list logo
