Bug 510537 - Allow application-specific button binds
Summary: Allow application-specific button binds
Status: RESOLVED DUPLICATE of bug 477671
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_tablet (other bugs)
Version First Reported In: 6.4.5
Platform: Arch Linux Linux
: NOR wishlist
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-10-12 20:53 UTC by Jan Bidler
Modified: 2025-11-27 23:19 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jan Bidler 2025-10-12 20:53:29 UTC
SUMMARY
I have a few applications that I want to set specific tablet-keybinds for. Currently I can't do that and have to do the workaround of:
- Go to systemsettings and change the keybind from "pass to application" to my desired bind
- Use application foo
- Go back to systemsettings and change the keybind back to "pass to application".

It'd be nice if I could set a specific "application foo" profile so that I don't have to constantly switch back and forth.


SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 6.4.5
KDE Frameworks Version: 6.19.0
Qt Version: 6.10.0
Kernel Version: 6.17.1-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 1600 Six-Core Processor
Memory: 16 GiB of RAM (15.6 GiB usable)
Graphics Processor: AMD Radeon RX 570 Series
Manufacturer: Gigabyte Technology Co., Ltd.
Product Name: B450M DS3H
Comment 1 David Redondo 2025-10-13 08:22:30 UTC
I think at this point applications should just handle tablet events themselves
Comment 2 Jan Bidler 2025-10-13 11:54:27 UTC
David Redondo: Some applications are sadly limited in how they interact with tablet events. [RNote](https://flathub.org/en/apps/com.github.flxzt.rnote) for example only lets you change them to a list of curated actions. 
I would naively also assume that there are probably some legacy apps out there that would cause problems as well.
Comment 3 Joshua Goins 2025-11-27 21:58:49 UTC
Right, it's a balance of how long we want to wait for apps to adopt their own keybinds. I personally am still in the wait camp, so this is not my priority at the moment.
Comment 4 Joshua Goins 2025-11-27 23:19:01 UTC
Moving this to the other issue since this is also profile related.

*** This bug has been marked as a duplicate of bug 477671 ***