Type of device* : Graphic Tablet
Brand and version of the device: Wacom One S
System** : Windows 10
* graphics tablet/display tablet/2-in-1 laptop/Android tablet
** Windows/Linux/Mac/Android, + version (you’ll find it in Help -> Show system information for bug reports)
Description of the issue (you can include screenshots): Hello,
Krita is completely ignoring my Wacom center Pen settings. I am trying to disable the pen buttons because they get in my way. I have disabled them in the Wacom Center, they don’t work anywhere else but in Krita. I have so far tried to make a profile for Krita in WC, I’ve tried re-installing both Krita and the Wacom drivers and I have tried to disable the buttons inside of Krita as well. None of that solved the issue. What can I do here?
Do you have a Krita profile set up in Wacom? In that profile, is Windows Ink turned off (it should be).
When you are in the Wacom Krita profile, what are the settings for the pen button?
The difference between Krita and some other apps is that Krita does not communicate with any tablet or pen. It takes all its signals from the operating system. I don’t know if that bit of info will help you.
Yes, I have a Krita profile setup with Windows Ink being on or off not making a difference. The settings for the pen buttons are “Disabled”. It doesn’t matter what settings I choose the buttons to perform, Krita completely ignores any pen settings.
I wish I had an answer for you. The thing is, Krita doesn’t know what your pen settings are. Somehow, the operating system is still getting button signals that are being passed to Krita via the Wacom driver.
More info that may lend clues is that Krita and the Wacom driver have to match – i.e. both need Windows Ink turned off. In Krita, choose WinTab, then you must close Krita or the change doesn’t take effect. While Krita is closed, turn off Windows Ink in Wacom, then restart your device. Once the device is restarted, then you can reopen Krita and see if that helped.
Re-installing Krita usually is the biggest waste of time, because you only exchange a working installation with a working installation, if you do not reset the kritarc and in your case also the kritashortcutsrc, that both are found at the very end in your %LOCALAPPDATA% folder.
Did you do that? If not, you can try the following:
Since your settings seem to be of no worth for you, you can delete both files. In the case you want to hold your kritashortcutsrc and kritarc for backup purposes and rename them to something like kritarc.old and kritashortcutsrc.old, you have to enable the view of file name extensions in the “View” menu of your Explorer, because if you don’t do that Windows will give them extensions Windows believes they would be right but is wrong.
If you want to do the above, you have to close Krita and can restart it after you renamed or deleted the files named above.
Because I never heard of an issue like yours, I can not say if it will solve your issue, but at least the chance is significantly higher than re-installing Krita where the chance for success is about 0.00001% or less. Re-installations may only help in those cases where users did what they NEVER should do without really knowing what they are doing, what most don’t, even those who believe that: → do any kind of manipulations in Krita’s installation folder!
No matter if you copied, overwrote, deleted or edited files in Krita’s installation directory, only then a re-installation makes sense, but it is mandatory to do it in combination with a reset / rebuild of Krita’s settings files and probably also (additionally) together with its resource database resourcecache.sqlite in %APPDATA%\krita\, if you don’t do that it will be a waste of time.
@sooz: For me too, this issue is an absolutely new one, a novelty!
And I have no idea what may cause it. It is one of the issues where I would like to be present where it happens, to be able to inspect the machine and the peripherals myself.
In Krita > Settings > Tablet Settings > Tablet Input API > Use mouse events for right click- and middle clicks. That should be ticked. Buttons are finally disabled.