| Summary: | Allow application-specific button binds | ||
|---|---|---|---|
| Product: | [Applications] systemsettings | Reporter: | Jan Bidler <janbidler00> |
| Component: | kcm_tablet | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | wishlist | CC: | akselmo, aleixpol, josh, kde, nate |
| Priority: | NOR | ||
| Version First Reported In: | 6.4.5 | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Jan Bidler
2025-10-12 20:53:29 UTC
I think at this point applications should just handle tablet events themselves 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. 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. Moving this to the other issue since this is also profile related. *** This bug has been marked as a duplicate of bug 477671 *** |