Bug 477752

Created attachment 163637 [details]
screenshot showing the touch ring configuration under x11

See my comment in https://bugs.kde.org/show_bug.cgi?id=477787#c4

Replicating what we have on X11 would be possible, but apps directly supporting touch rings would improve the UX around it

A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/3098

A possibly relevant merge request was started @ https://invent.kde.org/plasma/kwin/-/merge_requests/7879

Git commit 33ef5e79b8be6a26efc9a1f891d2c1b97e6a860d by Joshua Goins.
Committed on 28/08/2025 at 13:14.
Pushed by redstrate into branch 'master'.

ButtonsRebindsFilter: Add support for rebinding to tablet touch rings

This is specifically for the touch rings seen on Wacom tablets. How they
work is that can they switch "modes" (which is already handled) and each
mode can have it's own rebind. This is only for rings and eventually
strips, so fortunately we do not have to retroactively add mode support
for our bindings.

Libinput only gives us ring positions in degrees, and leaves the
interpretation up to us. I have to add some extra state to
ButtonRebindsFilter to keep track of the initial ring position, but I
think it works well enough for now.

To add to the complexity a bit, I added a way to configure the
"sensitivity" or "speed" of axis keybinds which is really only useful
for rings. This does break existing axis keybinds for dials, but no one
but developers (like me) would have set any at this point.

M  +45   -1    autotests/integration/buttonrebind_test.cpp
M  +1    -0    autotests/integration/kwin_wayland_test.h
M  +6    -0    autotests/integration/test_helpers.cpp
M  +67   -12   src/plugins/buttonrebinds/buttonrebindsfilter.cpp
M  +7    -5    src/plugins/buttonrebinds/buttonrebindsfilter.h

https://invent.kde.org/plasma/kwin/-/commit/33ef5e79b8be6a26efc9a1f891d2c1b97e6a860d

Git commit 33813235747e3b601f3643e25a22d85fa50c7b00 by Joshua Goins.
Committed on 30/08/2025 at 17:12.
Pushed by redstrate into branch 'master'.

kcms/tablet: Allow assigning shortcuts to tablet touch rings

This exposes UI to rebind touch rings, like those seen on Wacom tablets.
They are most similar to dials, where you can: disable them, use as a
scroll wheel or bind to two arbitrary keybinds.
VERSION-FIXED-IN: 6.5.0

M  +1    -0    kcms/libkwindevices/inputdevice.cpp
M  +22   -0    kcms/libkwindevices/inputdevice.h
M  +14   -4    kcms/tablet/inputsequence.cpp
M  +11   -0    kcms/tablet/inputsequence.h
M  +55   -25   kcms/tablet/kcmtablet.cpp
M  +3    -1    kcms/tablet/kcmtablet.h
M  +18   -3    kcms/tablet/ui/ActionDialog.qml
M  +67   -0    kcms/tablet/ui/PadTab.qml

https://invent.kde.org/plasma/plasma-desktop/-/commit/33813235747e3b601f3643e25a22d85fa50c7b00

Hi all,

I recently got the update for Plasma 6.5.1 on my distribution and had been looking forward to testing touch ring mouse scrolling again with a Wacom Intuos Pro L PTH-860. I observe the following.

1. Touch direction for scrolling is inverted compared to the X11 implementation I used for many years. X11 has clockwise=down, counterclockwise=up. This seems not configurable currently.

2. More importantly: Scrolling is hyper sensitive. The smallest detectable input on the touch ring turns into the equivalent of at least 5 mouse scrolls with a regular mouse with default settings. Scrolling through a quarter of the touch ring (so a quarter-circle motion) is equivalent to about 7 page up/down keypresses. Unlike the keyboard keys option there seems to be no option to configure the scrolling speed and the default being so sensitive makes is realistically unusable and incredibly jerky.

Could someone else also share their experience? Perhaps it is specific to my tablet or config somehow?

Thanks!