Bug 95480 - [RFE] Trackpoint: «button scrolling» with no button pressed
Summary: [RFE] Trackpoint: «button scrolling» with no button pressed
Status: RESOLVED WONTFIX
Alias: None
Product: Wayland
Classification: Unclassified
Component: libinput (show other bugs)
Version: 1.2.x
Hardware: Other All
: medium normal
Assignee: Wayland bug list
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-05-19 02:19 UTC by exc
Modified: 2016-06-13 00:05 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments

Description exc 2016-05-19 02:19:55 UTC
With x86-input-evdev setting property "Evdev Wheel Emulation Button" to 0 means scrolling without pressing buttons. Please implement same in libinput. Thanks in advance.
Comment 1 Peter Hutterer 2016-06-13 00:05:01 UTC
Not planning to implement this at this point, sorry. It's an interesting feature, but my slate is so full right now that I won't get to this.

implementation-wise: I'm not sure that wedging this into our current scroll button approach would be sensible, it is better to have a new scroll method "always" (or similar naming) since a similar request has come up for touchpads in the past.

but I do question whether the effort is worth the benefit. Yes, it saves you a button press when you need to scroll but it doesn't come for free on the maintenance side of things. and the cost is an ongoing one since we cannot ever retire this feature once it's merged.

this is also a feature we cannot ever enable by default, so you'll need something providing access to the configuration option. this is easy enough with the xorg.conf approach, but you'll have to convince a few wayland compositors first that they too will expose this in some manner. otherwise it will just end up being an unreachable configuration option in the long run that costs us maintenance effort but is not actually usable by the majority of users.


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.