| Summary: | [Android] Physical Keyboard input is broken under Android | ||
|---|---|---|---|
| Product: | [Applications] krita | Reporter: | Tyson Tan <tysontanx> |
| Component: | Shortcuts and Canvas Input Settings | Assignee: | Krita Bugs <krita-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | dra.w.p.il.e+bugskde, matheushcdias |
| Priority: | NOR | ||
| Version First Reported In: | nightly build (please specify the git hash!) | ||
| Target Milestone: | --- | ||
| Platform: | Android | ||
| OS: | Android 13.x | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | Invalid recoring of key combination when a modifier is pressed | ||
|
Description
Tyson Tan
2022-12-11 17:22:51 UTC
I have investigated deeper into this issue. It seems many physical keyboard related things have broken under Android. They are probably all input method related, and they affect English users too. 1) English inputs are always uppercased. It was likely to be caused by Android's English input method's Auto-Uppercase function. After turning off all those "smart" options, I had restart the device for it to take effect. On the other hand, the on-screen virtual keyboard can input always letters correctly. 2) When the issue in (1) was happening, I was unable to input anything in Krita's "Search" boxes, like the one on Shortcut page in Configure Krita dialogue. On the other hand, I was able to input in Layer name fields, although they were all uppercased. 3) Shortcut customization cannot take key combinations with modifiers correctly. After pressing the button to record a shortcut, a key combination with any modifier will record multiple inputs, which Krita will not accept as valid input. For example, if I pressed "Ctrl+Q", the Shortcut Krita took was actually "Ctrl+Q,Ctrl+...(cannot be seen)". This shortcut would not be displayed in the "Short" or "Alternate" columns, and Krita would not remember it. This makes Shortcut customization with modifiers impossible under Android. Appenix to Comment 1: After a factory reset, the issue where English inputs are always uppercased did not happen by default. The device came with One UI 4.0, maybe the updated version 5.0 has default settings that solved the problem. Other issues remained the same. Workaround of Shift key conflict: 1) Use the samsung labeled, fallback input method. Disable all 3rd party input methods. Curiously, this is NOT the default setting. The device comes with a VERY popular 3rd party input method (Sogou) preinstalled, and uses that as the default). 2) Remove all input languages except English. In that way, Krita will never get confused by pressing Shift. Created attachment 154626 [details]
Invalid recoring of key combination when a modifier is pressed
In this screenshot, I was trying to assign the key combination "Ctrl+Q" to an action. However, it didn't just record "Ctrl+Q", but seemingly multiple of the same combination as a sequence (because there is comma between them). Notice how the key combination didn't show up in the Shortcut column, for some reason. This shortcut won't be remembered after clicking OK.
The issue mentioned in Comment 4 is neither language or input method related. A pure English environment would have triggered the same thing. Can confirm, had this issue on my tablet when I tried using Gboard instead of the default samsung keyboard. The keyboard popup always appeared when I had Gboard on and I was unable to use shortcuts. I didn't have to disable Gboard for it to work properly, only switched back to Samsung keyboard and it was fixed. It happens on any language too. I think this may be fixed by the same patch that fixed Bug 431681, since that does exactly what you describe with regards to input methods and getting rid of them when unfocusing a text input. Could you check whether this works for you in the nightlies and, if not, what parts of the original report still don't work? (In reply to dra.w.p.il.e+bugskde from comment #7) > I think this may be fixed by the same patch that fixed Bug 431681, since > that does exactly what you describe with regards to input methods and > getting rid of them when unfocusing a text input. Could you check whether > this works for you in the nightlies and, if not, what parts of the original > report still don't work? (3) in Comment 1 is still happening. Now a new issue has arised: I cannot use input method in the text tool's on-canvas input box anymore. 🐛🧹 Thanks for your comment! Automatically switching the status to REPORTED so the team can perform further triage. In the future you may also do this yourself when providing needed information. A possibly relevant merge request was started @ https://invent.kde.org/graphics/krita/-/merge_requests/2558 (In reply to Tyson Tan from comment #9) > Now a new issue has arised: I cannot use input method in the text tool's > on-canvas input box anymore. This also happens on Windows, so it should be an unrelated issue. I moved that to Bug 513079. The problem with the shortcut edit not realizing you let go of modifiers is fixed. (In reply to dra.w.p.il.e+bugskde from comment #12) > (In reply to Tyson Tan from comment #9) > > Now a new issue has arised: I cannot use input method in the text tool's > > on-canvas input box anymore. > > This also happens on Windows, so it should be an unrelated issue. I moved > that to Bug 513079. > > The problem with the shortcut edit not realizing you let go of modifiers is > fixed. Yes, it's fixed now. Thank you, Carsten! :) |