Bug 380920

Summary: pen buttons on intuos
Product: [Applications] krita Reporter: nicholasgregg94
Component: Tablets (tablet issues are only very rarely bugs in Krita!)Assignee: Krita Bugs <krita-bugs-null>
Status: RESOLVED FIXED    
Severity: normal CC: halla
Priority: NOR    
Version First Reported In: 3.1.4   
Target Milestone: ---   
Platform: Microsoft Windows   
OS: Microsoft Windows   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description nicholasgregg94 2017-06-07 02:29:18 UTC
Krita seems to be overiding my pen buttons, the top button in krita always seems to be the right button, even if I set it to disabled in wacom settings it still registers as right click in krita. The bottom button won't work no matter what I define it as, I've used the tablet with no problem in other programs it's just this one that it doesn't work.

I've tried reinstalling the drivers for my wacom device and uninstalling\reinstalling krita but neither changed anything
Comment 1 Halla Rempt 2017-06-07 07:09:02 UTC
Are you really on Linux? 

I've never tried disabling a button completely, but if Krita registers a button event, then a button is sent. And on all the os'es I've tried, both buttons work. By default, the bottom button pan, the top button pops up the popup palette. There is no special code for configuring tablet stuff in Krita at all.

There are a couple of similar issues reported, for Windows, but I would first try resetting the tablet driver settings and then making a special profile for Krita. 

Note that uninstalling and reinstalling Krita does precisely nothing. You can try to reset Krita's configuration, which is not done by uninstall/reinstall: https://docs.krita.org/KritaFAQ#Resetting_Krita_configuration
Comment 2 nicholasgregg94 2017-06-07 12:18:22 UTC
I'm on windows
Comment 3 nicholasgregg94 2017-06-07 12:20:51 UTC
I've tried making a special profile for krita in the wacom tablet settings if that's what your referring to but nothing changed
Comment 4 Halla Rempt 2019-04-16 10:25:18 UTC
We've gone through multiple rewrites of the tablet support for Windows now, so I don't think this bug is still relevant.