Hello!

I'm using a Wacom Intous on Windows 7.

1)
From PS I'm pretty used to being able to hold a key on my stylus to erase.
After googling for a while and figuring out all sorts of neat tricks, I also found the "Ten Brushes" plugin, which works really nicely, but there is no option to go back to the previous brush/preset after releasing the key again.

I know there's "switch to last brush", but that's not really what I need since I don't want to hit another key after being done erasing.

Is there any way to enable some kind of "activate while holding key" functionality?
Switching to a specific preset when the forward stylus key is pressed down, and then when it is released going back to the previously selected brush.

2)
Also, how do I consistently set hotkeys?
I want to pan the canvas using the upper stylus button.
Since "Scroll and Move" in the Wacom Tablet Driver doesn't work, I switched that upper-key to F11 in the driver; and then I went to the krita settings and set it up like this:


That works fine when using the mouse (holding MMB pans the canvas).
But it only worked fine one time, and after restarting Krita it only shows the "hand" but won't actually pan the canvas when the stylus moves on the tablet.
What can I do to fix this? I have tried setting the settings again and restarting my computer, restarting Krita, ... but I can't get it to work anymore.
Any ideas?

3)
It seems like "application defined" and "4.th Click" and "5.th Click" are all not correctly recognized by Krita. The first one doesn't get detected in the settings dialog. And the other two are detected as forward/backwards button (which should be ok, because that's what they are on my mouse) but they also don't actually do anything when pressed.
Am I doing something wrong?

https://bugs.kde.org/show_bug.cgi?id=350162
https://bugs.kde.org/show_bug.cgi?id=351605
https://bugs.kde.org/show_bug.cgi?id=337135

Hmm, I'm running into all of those bugs here I think.
Looking at the created/modified dates, it seems like this won't be fixed soon.
It's a shame since Krita is so damn good. But not being able to pan and erase using the stylus is pretty much a deal breaker for me

If anyone has any suggestions or ideas, please let me know!

Thanks for looking up the bug reports! That at least let me resolve one as a duplicate of the other

boudewijn wrote:Thanks for looking up the bug reports! That at least let me resolve one as a duplicate of the other

Is there any hope in getting those problems fixed?

I remember reading about some sort of input debug tool that records some lowlevel driver event stuff from the tablet.
Do you think I should try that and report back what I found?

The guy who also did this later figured out that the correct inputs are actually received by krita, but that it rejects them because they are not coming from the correct device. So emulating some key-presses won't work in the canvas because it sees "Mouse 3" and thinks "that's a key from the mouse, but it got sent by some wacom driver thing, better reject it".

The strange thing is though that stuff works in the key-setup dialog.
That would at least fix paning.

But the other problems (actions on release of a key) sound like they're harder to fix. Adding a whole new way to let the user map to stuff on keydown as well as keyup? Or maybe that can be avoided by simply having "Eraser" as option as before but renaming it to "Eraser (Toggle)", and then adding a new "Eraser (While holding)"? So simply two options, instead of one option with different "modes".

Also, how does Krita even know about the eraser function of the wacom tablet? As far as I know there's no key on a normal keyboard that would mean "eraser mode", so does the tablet send some strange custom code for which Krita has special handling for?
And how would I change what brush actually gets selected when that is received? From my experience it sometimes selects eraser soft, and sometimes the normal circle eraser...

Please let me know what I can do to help.

We do want to spend more time this year on fixing issues than on creating new features, but whether this bug will have any priority... My first priority is fixing the resources and tagging issues.

But Krita is open source... All it needs is for someone who experiences the bug to make the time and start debugging and fixing the issue.

boudewijn wrote:We do want to spend more time this year on fixing issues than on creating new features, but whether this bug will have any priority... My first priority is fixing the resources and tagging issues.

But Krita is open source... All it needs is for someone who experiences the bug to make the time and start debugging and fixing the issue.

Ugh.. I see
Sadly don't know enough about programming to fix such issues.
I can try but it will likely end up being a huge waste of time for everyone involved.

What alternate workflows do people use to work around those issues while maintaining speed? Do they map some button to the context menu and then pick out the eraser? Sounds like a huge interruption when drawing so surely there must be a better way everyone uses, no?

I have a key on the tablet itself mapped to E, which enables the eraser mode. And there's the 10 brushes plugin which might be worth investigating.

boudewijn wrote:I have a key on the tablet itself mapped to E, which enables the eraser mode. And there's the 10 brushes plugin which might be worth investigating.

Hey there again

I have taken a look at the ten brushes plugin thing.
It seems to be written in python, I looked up the basics of that and it seems to be sorta, kinda doable, I guess.

So here's what I don't get:

At no point in all those files does the plugin specify what keys it wants to handle.
For me in Krita ten brushes is registered as CTRL+ALT+0 etc...
But I can't see that in the code anywhere, is that like... the default for key combos created from plugins?

Anyway, that's not really important anyway, just something I'd like to know.
Since I want to deal with button presses and releases I think I need a way to do some code when that happens.
But all I can see is that an "action" is connected, and I searched around a lot on that documentation page and didn't find anything related to button presses and releases.

If I could find that, then I guess I would somehow save what I currently have selected in a file, and then load that again when the button is released.
Does that make sense?

I feel a bit lost to be honest though, but I think once I got the "parts" I can somehow assemble a script that does what I need...