https://bugs.kde.org/show_bug.cgi?id=521611
--- Comment #10 from [email protected] --- > Since libinput now supports this, is this a kwin thing, or something else? > What needs to be recoded or patched in order to get this fixed? It's a kwin thing. They need to add the ability for the tablet configuration to recognize the grouping of signals that your stylus sends when you click that button (proximity-out + invert + proximity-in, possibly more), group it together into a single command ('ms_eraser' or whatever), and replace it with whatever you specify. I honestly have no much work this requires, or how much of it is libinput and how much is kwin. I'm going to look at the code and see if I can figure something out, but I have minimal programming knowledge. > This makes > a lot of styluses unusable or - more annoyingly - semi-usable, which is a > massive distraction to the creative workflow. This is NOT a feature > request, or a nice-to-have. This is ESSENTIAL. So, anything I can do on my > end to help it along, I'm in. As a temporary alternative, you might want to check out OpenTabletDriver, https://opentabletdriver.net/ They don't list your tablet on the site, but their Discord has configurations for lots of devices that the devs and the users have added support for. You might have good results, it's worked nicely for me. -- You are receiving this mail because: You are watching all bug changes.
