SUMMARY Being right handed, this happens a lot. After pressing the textbox to manually input the pagezoom percentage (at the bottom right) my bluetooth keyboard becomes unusable even after tapping off the pagezoom textbox. Whenever you press an shortcut like "E" for the eraser, the small autocorrect options would appear on the bottom of the screen, as it would appear if you were typing something. Dismissing the keyboard doesn't work either as pressing a hotkey would simply bring the autocorrect options back up, as if were stuck entering something into a textbox. The only hotkeys that do work are hotkeys with modifiers like undo (ctrl-z) anything else just brings back up the autocorrect options. STEPS TO REPRODUCE 1. Open Krita and have a bluetooth keyboard connected (in my testing this happens with regular keyboards too) 2. tap the pagezoom box at the bottom right of the screen. The autocorrect options of whatever keyboard you're using should appear. 3. Tap out of the box and attempt to use any non-modifier hotkey like E for eraser. OBSERVED RESULT The autocorrection options pop up as if you were still typing something; single button hotkeys only seem to enter text into thie "invisible" textbox EXPECTED RESULT The hotkeys work as normal SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: Using the android version downloaded from here:https://krita.org/en/item/second-beta-for-krita-4-4-2/. I am on a Samsung Galaxy Tab S6 Lite. ADDITIONAL INFORMATION None.
A quick update, this bug seems to occur with ALL textbox inputs. Whether youre manually entering the size of a your brush or changing the name of a layer, entering the text box will render you unable to use hotkeys from there on out. The only fix is to save your work and completely restart krita, praying that you don't accidentally touch a textbox that session. Hope this helps!
Hi! From what you describe it seems like a rather serious issue. However I haven't been able to reproduce it. Could you share a recording of this buggy action? Though nothing specific to Input Method changed in Krita 4.4.3 there were few changes which handled focus properly. Could you try the newer release, maybe that fixed it?
(In reply to Sharaf from comment #2) > Hi! > > From what you describe it seems like a rather serious issue. However I > haven't been able to reproduce it. Could you share a recording of this buggy > action? > > Though nothing specific to Input Method changed in Krita 4.4.3 there were > few changes which handled focus properly. Could you try the newer release, > maybe that fixed it? I've attached a video of me explaining the error, apologies for the incorrect terminologies I'm hoping my point still gets accross. The app is still usable just very very annoying when this happens https://drive.google.com/file/d/1q4t2QfwvhAF5nM5qQb8wzrYzKNQOhccZ/view?usp=drivesdk Hopefully this helps I was wondering when this bug would be addressed!
(In reply to Dorian Zambo from comment #4) > (In reply to Sharaf from comment #2) > > Hi! > > > > From what you describe it seems like a rather serious issue. However I > > haven't been able to reproduce it. Could you share a recording of this buggy > > action? > > > > Though nothing specific to Input Method changed in Krita 4.4.3 there were > > few changes which handled focus properly. Could you try the newer release, > > maybe that fixed it? > > I've attached a video of me explaining the error, apologies for the > incorrect terminologies I'm hoping my point still gets accross. The app is > still usable just very very annoying when this happens > > https://drive.google.com/file/d/1q4t2QfwvhAF5nM5qQb8wzrYzKNQOhccZ/ > view?usp=drivesdk > > Hopefully this helps I was wondering when this bug would be addressed! I can't reproduce the exact issue but I do see some problems with using physical keyboard. So, I'll set this to confirmed. Also what soft-keyboard is that? Is it the default one from Samsung? PS: Seems somewhat related to https://bugs.kde.org/show_bug.cgi?id=432455
(In reply to Sharaf from comment #5) > (In reply to Dorian Zambo from comment #4) > > (In reply to Sharaf from comment #2) > > > Hi! > > > > > > From what you describe it seems like a rather serious issue. However I > > > haven't been able to reproduce it. Could you share a recording of this buggy > > > action? > > > > > > Though nothing specific to Input Method changed in Krita 4.4.3 there were > > > few changes which handled focus properly. Could you try the newer release, > > > maybe that fixed it? > > > > I've attached a video of me explaining the error, apologies for the > > incorrect terminologies I'm hoping my point still gets accross. The app is > > still usable just very very annoying when this happens > > > > https://drive.google.com/file/d/1q4t2QfwvhAF5nM5qQb8wzrYzKNQOhccZ/ > > view?usp=drivesdk > > > > Hopefully this helps I was wondering when this bug would be addressed! > > I can't reproduce the exact issue but I do see some problems with using > physical keyboard. So, I'll set this to confirmed. > > Also what soft-keyboard is that? Is it the default one from Samsung? > > PS: Seems somewhat related to https://bugs.kde.org/show_bug.cgi?id=432455 The keyboard I was using in the video is just a regular USB keyboard I connected to my tablet using an adapter. This also happens with my bluetooth keyboard as well, and even if I'm not using a keyboard at all, and enter a textbox the same issue occurs. Due to this, I doubt the keyboard used is a factor here. Also for the issue linked, I tried the fix mentioned and it didn't seem to work at all for my issue. I may be doing something wrong but I believe they may be different issues.
(In reply to Dorian Zambo from comment #6) > (In reply to Sharaf from comment #5) > > (In reply to Dorian Zambo from comment #4) > > > (In reply to Sharaf from comment #2) > > > > Hi! > > > > > > > > From what you describe it seems like a rather serious issue. However I > > > > haven't been able to reproduce it. Could you share a recording of this buggy > > > > action? > > > > > > > > Though nothing specific to Input Method changed in Krita 4.4.3 there were > > > > few changes which handled focus properly. Could you try the newer release, > > > > maybe that fixed it? > > > > > > I've attached a video of me explaining the error, apologies for the > > > incorrect terminologies I'm hoping my point still gets accross. The app is > > > still usable just very very annoying when this happens > > > > > > https://drive.google.com/file/d/1q4t2QfwvhAF5nM5qQb8wzrYzKNQOhccZ/ > > > view?usp=drivesdk > > > > > > Hopefully this helps I was wondering when this bug would be addressed! > > > > I can't reproduce the exact issue but I do see some problems with using > > physical keyboard. So, I'll set this to confirmed. > > > > Also what soft-keyboard is that? Is it the default one from Samsung? > > > > PS: Seems somewhat related to https://bugs.kde.org/show_bug.cgi?id=432455 > > The keyboard I was using in the video is just a regular USB keyboard I > connected to my tablet using an adapter. This also happens with my bluetooth > keyboard as well, and even if I'm not using a keyboard at all, and enter a > textbox the same issue occurs. Due to this, I doubt the keyboard used is a > factor here. > The reason I asked this was some soft-keyboards tend to buffer the text so they can predict what you're typing or do auto-corrections -- Yes, even for a physical keyboard.
Update to this bug, I've learned that you don't need to restart Krita to get everything working again, you just need to go to the the three dots -> settings-> configure Krita menu. Once you've opened the menu, closing it by pressing cancel will render all 1 button hotkeys usable again. I really don't know how this works but I hope this helps!