Summary: | Enable / disable tapping by number of fingers | ||
---|---|---|---|
Product: | Wayland | Reporter: | AMM <ammdispose-fedora> |
Component: | libinput | Assignee: | Wayland bug list <wayland-bugs> |
Status: | RESOLVED WONTFIX | QA Contact: | |
Severity: | normal | ||
Priority: | medium | CC: | ammdispose-fedora, anon.amish, peter.hutterer |
Version: | unspecified | ||
Hardware: | Other | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
AMM
2017-02-10 10:03:16 UTC
there is currently no option to only enable parts of the tapping code, e.g. for three-fingers only and as you found, the ButtonMapping one is for any button coming out of libinput, so it affects real buttons and tapping equally. In short, the exact feature you're looking for doesn't exist in libinput. If your device is a clickpad, you may be happy enough enabling clickfingers or using the middle button area/emulation instead, see the link below. https://wayland.freedesktop.org/libinput/doc/latest/clickpad_softbuttons.html But the exact feature you're currently using in synaptics is unlikely to ever be implemented in libinput, sorry. I respect your decision to not have this feature. But just last request (or suggestion) for this There is already an option called: TappingButtonMap Currently it allows only two values lrm or lmr Can it not be extended, like instead of fixed words (lrm OR lmr) it can be 3 letter word from l, m, r and d (where d means disable) user can set it to ddm (will solve my feature request) or rlm (single click is right click) or mlr (single click is middle click) or even dlr (for those who like tapping but want to avoid single finger accidental touch) This should also make code more simpler and more flexible without too much addition to code. Thank you in advance. PS: Sorry to re-open the ticket as I do not know how to bring it into ur notice without re-opening it. sorry, still giving this a 'no'. I don't think it would make the state much simpler since we not only have to keep the whole tap state machine but rather add to it the special code paths where one finger doesn't trigger bugs. Which then affects other things, as tapping starts other features may get disabled so we don't consider a tapping finger as palm, etc. The better option to address this is to figure out why you're getting accidental taps when you're not intending to tap and fix that misdetection. Is this for real? This is possibly the most annoying "feature" one could possibly think of and an obvious regression. Yes, it's for real. Coming here out of the blue and complaining in this tone won't get your bug fixed. I strongly recommend keeping your language neutral and technical. libinput has moved to gitlab, any new bugs should be filed at http://gitlab.freedesktop.org/libinput/libinput/ |
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.