Open crocodisle opened 1 month ago
Hi
For now -quick test- I'm not able to reproduce this case.
When you say the keys are unboundn it means they're not available anymore in brush settings in BuliBrushSwitch if I understand.
In this case, does they appear in Krita's shortcut settings? Example:
On my side I'm on v1.2.0 (not released yet... you can switch to 1.2.0 branch and download zip to test if needed, but I'm not sure it will change a lot about shortcut) with Krita 5.2.2 AppImage.
I've to update to 5.2.3 to check what happen.
Grum999
Krita Version: 5.2.3 Operating System: Debian GNU/Linux 12 (bookworm)
Kernel: Linux 6.1.0-22-amd64 Architecture: x86-64 BuliBrushSettings Plugin Version: v1.1.0 Python Version: 3.11.9
Krita installed via flatpak. Plugin was installed via .zip file.
I set up my configuration in two ways:
There were only two brushes, a normal brush and an eraser. Each brush had their own hotkey assigned in the Buli Brush settings menu. After a minute or two of switching back and forth between the brushes, the hotkeys would stop working. Checking in the buli brush interface would reveal it to appear as if the brushes were unbound completely. Rebinding the brushes worked for a period of time.
I set up the brushes each in their own folder and put hotkeys on the folders instead. This had similar behavior until they stopped working completely, however they would still be listed as the keys being bound.
Steps taken: Turned off other scripts, restarted krita. Behavior persists.
I checked the titles of previous issues but none of them seem to be regarding this. If you need any more information, I'd be happy to provide it.