From 44fecb9a98510619bf8a7ec837c34cb126100c95 Mon Sep 17 00:00:00 2001 From: Peter Hutterer Date: Mon, 6 Jan 2025 14:39:28 +1000 Subject: [PATCH] doc/user: link to the explanation why we can't change the tap default We don't have an API for "device really should have tapping enabled" so right now the only indicator of whether that's the case is when the device has tapping enabled by default. This kind of prevents us from switching the default, so let's at least link to the comment explaining this. Part-of: --- doc/user/tapping.rst | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/doc/user/tapping.rst b/doc/user/tapping.rst index 5c02ca6e..14d273b4 100644 --- a/doc/user/tapping.rst +++ b/doc/user/tapping.rst @@ -34,6 +34,10 @@ Tapping is **enabled** by default on devices where tapping is the only method to trigger button clicks. This includes devices without physical buttons such as touch-capable graphics tablets. +.. note:: Unfortunately due to the current API design, devices that require + tapping effectively prevent us from changing this default. For details see + `this comment `_. + Tapping can be enabled/disabled on a per-device basis. See **libinput_device_config_tap_set_enabled()** for details.