https://bugs.kde.org/show_bug.cgi?id=481737
David Redondo <k...@david-redondo.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |k...@david-redondo.de
--- Comment #1 from David Redondo <k...@david-redondo.de> ---
That's on the app and kinda hard to do.
These evdev events indicate not button presses but that a certain tool is in
use with the device see
https://www.kernel.org/doc/Documentation/input/event-codes.txt
Quoting
* BTN_TOOL_<name>:
- These codes are used in conjunction with input trackpads, tablets, and
touchscreens. These devices may be used with fingers, pens, or other tools.
When an event occurs and a tool is used, the corresponding BTN_TOOL_<name>
code should be set to a value of 1. When the tool is no longer interacting
with the input device, the BTN_TOOL_<name> code should be reset to 0. All
trackpads, tablets, and touchscreens should use at least one
BTN_TOOL_<name>
code when events are generated.
The compositor just sees a "proximity in" event for a tool.
I think it's not possible to know in general if a tool is the same physical
object or not.
Further reading:
https://gitlab.freedesktop.org/libinput/libinput/-/issues/841#note_1699093
https://wayland.freedesktop.org/libinput/doc/1.12.0/tablet-support.html
I think at some point the user should know what the buttons on their hardware
do. Given that we did not receive bug reports about that so far I would make a
guess that if you buy a drawing tablet that behavior would be documented and/or
known by artists.
--
You are receiving this mail because:
You are watching all bug changes.
