-
-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TextInput limited to 1 character when Swype with word suggestion turned on #2694
Comments
I also can observe this bug, my setup: |
Likewise with Android 5.0.2 and otherwise the same as the previous commenter. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Is this bug not critical? In a nutshell, user input in textinput widgets is limited to text entry one character at a time - and swype-like gesture input as whole words is not working at all. |
Given that no one replied, it's probably because no one knows where exactly the issue is. But I expect it's somewhere in the sdl2 input events. |
Just tо summarize, if I understand correctly the situation is as follows:
|
Before a issue can be opened in the SDL repo, we should have a clear understanding of why it currently doesn't work as it may not be an SDL2 issue, but a kivy issue. So we'd need to understand how it's supposed to work in SDL2 and whether kivy is missing some interface. For reference, you can see related issues about selecting the keyboard type: #7130, #7231. |
With Swype with word suggestion turned on on my Android 2.3 phone, I can only enter a single character in a TextInput. If I try to enter more text, the character is always replaced by the last typed character.
The problem vanishes when turning word suggestion off, or by selecting Samsung's keyboard instead of Swype.
It would be great if this could be solved. (I'm using Kivy 1.9.)
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: