Summary: | No visual feedback when pressing stylus buttons that emit BTN_TOOL_PEN or BTN_TOOL_RUBBER | ||
---|---|---|---|
Product: | [Plasma] kwin | Reporter: | Nate Graham <nate> |
Component: | input | Assignee: | KWin default assignee <kwin-bugs-null> |
Status: | REPORTED --- | ||
Severity: | minor | CC: | kde |
Priority: | NOR | Keywords: | usability |
Version: | master | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Linux | ||
See Also: |
https://bugs.kde.org/show_bug.cgi?id=475704 https://bugs.kde.org/show_bug.cgi?id=469232 |
||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Nate Graham
2024-02-23 21:55:17 UTC
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. > I think at some point the user should know what the buttons on their hardware do. I feel called out! :D FWIW the pen in question is the one that came with my laptop, and it lives in a little garage. Hardware like this is of secondary importance compared to a standalone drawing tablet, so I think we can't expect the user to be so much of an expert in what the buttons of the pen do. Maybe Bug 469232 is enough, though. > Maybe Bug 469232 is enough, though.
I am not sure it's possible for these buttons because we don't actually see a button press but let's see.
For exmaple I have a pen and the eraser is at the top of it (like a physical pencil with eraser). These events are generated when I turn that pen around.
|