Hi guys. i’m someone who jumps around the canvas pretty rapidly, and i noticed this bug in 4.4.2 and above (does not happen in 4.4.1) that Krita will (pretty regularly) stop recognising that Spacebar is held down when making rapid panning/zooming movements, resulting in the color picker being activated (if CTRL is pressed down), or the tool in use before spacebar was pressed (usually the brush tool in my case). anyone else experience this? it makes using 4.4.2 very frustrating for me.
PC Specs: Core i7 3770, 24gb RAM and a Radeon HD 7770 GHZ edition. My tablet is a Huion Kamvas 13 2020.
Yeah I have a similar issue on 4.4.2 and now that 4.4.3 is released however the issue is still there. When I do the [spacebar + ctrl] / [spacebar + shift] thing sometimes the combinations aren’t detected as if I was not pressing any button and just drawing normally, resulting in me drawing lines by accident. As soon as I let go of [spacebar] and pressing it again the bug stopped temporarily then it happened again when I switching the combo with either [shift] or [ctrl] so I have to let go of the [spacebar] every single time which is pretty inconvenient.
The thing is if I do the combination without dragging or hovering my pen tablet the bug is gone, and also if I use my mouse along with said combination as well. That bug only happens if I use my pen tablet at the same time so I think it was a compatibility issue? I’m using XP Pen Star 03 Pro, don’t know if Wacom users has that issue as well though.
I have tried updating my tablet driver, reinstalling Krita, and even reinstalling Windows (all of these doesn’t fix the bug). Downgrading to 4.4.1 do work though, so it has to do with 4.4.2 and now 4.4.3.
My conclusion is the bug is a version bug, and my only option as of currently is downgrading to v4.4.1 until the devs released a stable version that fixes the bug because honestly this bug is pretty infuriating and demotivates me trying to finish my artwork. The devs are working for a version 5 of Krita, I hope the bug gets fixed along the way. Also sorry if my reply is too long to read lol.
Thanks for the tip, yeah I’ve tried the middle mouse function and no bug for that shortcut. The only problem being is that I cannot remap it to spacebar so I have to get used to it.
This happens to me too. I thought I was just doing miss clicks somehow. But this behaviour has happen for a long while. The tool getting stuck and having to press space-bar to unlock it after.
Not really, what seems slow about it? I have MMB mapped to the front switch on my pen, so it’s under my thumb always. If only MMB+click+drag zoomed in Krita, it’d be perfect.
@Karkovb_152 Does your tablet driver settings/config utility have any facility for creating different ‘profiles’ for different applications?
If it does you should create a profile for krita while krita is running.
If you’ve already done this, delete that profile, restart your PC and create a new profile for krita while krita is running.
Try doing the above with version 4.4.3 to see if that fixes it for 4.4.3.
I can’t think why mapping your stylus button to MMB instead of the Space key would noticeably more fluid, if that’s what you mean.
I haven’t tried it with a stylus but when using the mouse, Ctrl+MMB+drag will zoom and Shift+MMB+drag will rotate.
If you edit the Canvas Input Settings then it should be possible to have MMB+drag do a zoom. However, you’d have to remove that binding for pan as well. It gets confusing in there.
I have MMB mapped on my stylus because MMB is used for navigation in other software I use. MMB-drag seems to be a pretty standard gesture for panning, I think it’s the default in Krita as well. So I’m used to it, and also it is just one click vs. space plus click.
If I have to choose between MMB for pan or MMB for zoom, pan is more important.
So it is possible to set two mouse button presses at once to a shortcut. I hadn’t managed to do that before, somehow. But as you say, it only kind of works.
It’s a shot in the dark but I’d just try to disable the fixShortcutMatcherModifiersState call altogether. For all we know it could be what’s causing the issue, since it was introduced few months before the release of 4.4.2. (November 2020)
But damn, I don’t feel like spending a week building krita just to debug this.