Type of device* : Display Tablet & Mouse
Brand and version of the device: Huion Kamvas 22 Pro, Reddragon M913 Impact Elite mouse
System** : Linux Mint 22.1 Cinnamon
So back in windows 10, I used to be able to draw comfortably with one hand and zoom/pan with the middle mouse wheel with the other in between strokes with no issue. Now, there is a horrible noticable waiting period in which i have to lift my brush for the program to start listening to mouse things like scroll zoom/pan. It is ignoring any mouse input until I stop painting for a noticable period/lift my pen it seems - almost like the program is still listening for brush strokes, and not taking in mouse input? This applies similarly if the mouse is doing something, I need to stop for a second or two before taking pen inputs - completely throwing me off my groove.
Iām not trying to do both at once here - I was hoping to find a way to make it quick & snappy in that space between brushstrokes again for quick canvas movements as I draw without it being so āstickyā between inputs.
Hello @SadOtterEatsTofu and welcome to the forum!
Since it worked using Windows, it could be an issue with the drivers. Do you use Huionās drivers or drivers provided by your distro? Depending on your answer, you should try the counterpart of the one installed. Also, OpenTabletDriver can be a good alternative if you whether like the driver from Huion nor the one from your distro.
Reddragon mice can be tricky because of their drivers using Windows, at least those two I once had were not a great advantage, if this is also true on Linux I donāt know.Ā¹
Michelist
Ā¹ I used them with Windows standard drivers and additionally XMouseButtonControl a āniceā driver add-on that allowed me to use the 4th and 5th mouse button, this way I must not use their driver.
Thanks for the warm welcome,
It seems my distro had nothing set up initially so Iāve tried the OpenTabletDriver first, then had a go at the official Huion ones instead - problem still persists sadly, for now I am using OpenTablet because Huion disconnects/reconnects all my Bluetooth things for some reason. Both of them are still good for programming keys and working areas and whatnot.
Iāve also tried with a different mouse, and the problem persists.
Iāve booted into a minimal windows 11 install, and it works OK there so Iām a bit stumped as it would be a bit of a faff to dual boot to give up on the Linux version.
Any more tips?
(I really hope the cursor control mix up isnāt a Wayland thing, Iām now seeing some neighbouring issues about two cursor thingsā¦)
Oops, I was fallen asleep, and in between you edited your post three times.
And, yes, Wayland is still occasionally a buzzkill today.
Well then, letās post my ramblings anyway, maybe thereās something to it, because here I am stumbling around in the twilight for lack of expertise, LOL.
No, I donāt really have any new ideas here. As far as I know, Krita is supposed to receive the signals from the Human Interface Devices (HID) via a Qt library (API) that communicates with the respective OS, so Krita cannot control the process itself.
So it sounds like (since Krita is āonlyā a command recipient of this API, and thus quasi outside) that this API, which mediates between Krita and the operating system (since the API and not Krita is the instance that communicates with the HIDs connected to the operating system via their drivers), Krita under Linux can only tell the same story in a slightly different way, exclusively serially, instead of partially parallelized, or tells it, which makes the story a different one for you. For whatever reason.
I canāt say whether our users familiar with the Krita source code know and can say more about this, but if it is due to the API, then it would probably be a question of the part of the Qt source code concerning this API anyway.
For me, after my strokes, this has become a realm of mystery that I no longer understand (although I was never good at it). I sometimes have trouble with longer batch files, and most of the scripts these days.
Michelist
The edits were just my horrid typos and Wayland research, no worries!
Thank you for your help anyway, Iāll continue to keep an eye out for any Wayland support / general API updates.
Meanwhile if any more techy people can chime in Iām still here :')