On Sun, Apr 29, 2018 at 07:08:18PM -0600, Chris Murphy wrote: > On Sun, Apr 29, 2018 at 6:20 PM, Peter Hutterer > <peter.hutterer@xxxxxxxxx> wrote: > > > Chris: the previous gsetting was 'default' so if you ever changed it > > manually to 'areas' in the past (e.g. for debugging something), the change > > to a different default wouldn't affect you because you already have your > > own setting already. I strongly suspect that's the case for you, run this to > > verify: > > gsettings get org.gnome.desktop.peripherals.touchpad click-method > > If it says 'areas', you changed it at some point in the past.z > > > $ gsettings get org.gnome.desktop.peripherals.touchpad click-method > 'fingers' > > Only now do I grok "areas" and "fingers" in this screenshot as > referencing the two settings in the release notes *which uses neither > term* so I had no idea what it was referring to. > > https://drive.google.com/open?id=10uahu6XOownq7oJS8O2TXg7TvW6Yy1_h > > So the description there for "fingers" is what I've always experienced > on this laptop with Fedora 25 through 28, and Windows 10. I tap two > fingers at the same time to get a contextual menu. Meanwhile the > release notes say "keep one finger in contact with the touchpad and > tap with another finger" and that does nothing for me. Nothing > happens. And yet the release notes say it's the default. the release notes are inaccurate then. "tapping" has a specific meaning for touchpads [1], a short tap with a finger while *not* actually triggering a physical click. The changed default has no effect on tapping, only on clicking (and that only on clickpads). On windows tapping and clicking are interlinked (for good reasons) but libinput can have a two-finger click cause a different button than a two-finger tap. Cheers, Peter [1] https://wayland.freedesktop.org/libinput/doc/latest/tapping.html _______________________________________________ desktop mailing list -- desktop@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to desktop-leave@xxxxxxxxxxxxxxxxxxxxxxx
