Summary: | Middle-mouse panning does not work in some applications on ThinkPad touchpad | ||
---|---|---|---|
Product: | Wayland | Reporter: | Niko Montonen <montonen.niko> |
Component: | libinput | Assignee: | Wayland bug list <wayland-bugs> |
Status: | RESOLVED WONTFIX | QA Contact: | |
Severity: | enhancement | ||
Priority: | lowest | CC: | peter.hutterer |
Version: | unspecified | ||
Hardware: | x86-64 (AMD64) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Niko Montonen
2017-12-11 18:51:51 UTC
I have also opened a bug report on KiCad's bug report system, as there are so many layers between my input device (ThinkPad X220 touchpad) and the application (KiCad) that I'm not sure where to even begin. Given that both libinput and KiCad are giving me behavior that I consider inconsistent. https://bugs.launchpad.net/kicad/+bug/1737596 As per a user on the #wayland IRC, setting "libinput Scroll Method Enabled" to all zeroes (to disable the button scroll method) fixes this problem. But I'll be leaving this open so someone more knowledgeable can make a judgment call as to if enabling button scrolling by default is a good idea, when it can break applications like this. What you're seeing is the effect of button scrolling: https://wayland.freedesktop.org/libinput/doc/latest/scrolling.html#button_scrolling That's enabled on some devices, most notably trackpoints. And it's going to stay that way, sorry. It's very uncommon to have to middle button+pan but it's very common to have to scroll up/down. Note that there is *no* correct default, we simply have to chose which use-case doesn't work out of the box. And wWe're erring on the side of the more common use-case here. This is a default only, so it can be disabled. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.