Bug 97365

Summary: RFE: Add configurable Timeout prop to Middle Button Emulation
Product: Wayland Reporter: Torstein Husebø <torstein>
Component: libinputAssignee: Wayland bug list <wayland-bugs>
Status: RESOLVED MOVED QA Contact:
Severity: normal    
Priority: medium CC: peter.hutterer
Version: unspecified   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:

Description Torstein Husebø 2016-08-16 12:53:53 UTC
Using a laptop with AlpsPS/2 ALPS DualPoint TouchPad/Stick with Middle Button Emulation with xorg-input-synaptic exposes a property "Evdev Middle Button Timeout (277)"

I request that the same be added to libinput to tweak the timeout for detecting Middle Mouse click.
Comment 1 Peter Hutterer 2016-08-16 21:38:57 UTC
what timeout do you use?
Comment 2 Torstein Husebø 2016-08-24 07:43:38 UTC
Its listed at Evdev Middle Button Timeout (277):	50
Comment 3 Peter Hutterer 2016-08-24 08:07:01 UTC
that's the same libinput uses...

If you're ok with 50 ms right now, I don't understand why you want a toggle.
Comment 4 Thomas Martitz 2018-05-27 20:13:20 UTC
Hello. I'd like to ask that the toggle be implemented. 50ms is too low for me, more often than not I trigger lift or right click than middle mouse. I find that I need to concentrate on hitting the buttons correctly for what should be a complete no-brainer.

Please consider an option or increasing the timeout anyway.
Comment 5 Peter Hutterer 2018-05-30 01:36:28 UTC
What timeout did you use before and what timeout do you need? Can you measure the time between clicks please?
Comment 6 GitLab Migration User 2018-06-05 09:57:51 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/libinput/libinput/issues/2.

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.