You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Axmol version: 2.1.0
Tested on iPhone SE, version 15.6.1
XCode 15.0.1
UPDATE: also the GTextInput from fairy does the same.
When a TextField is in focus, the GLView does not receive touches, hence, when tapping on a button (or anything else) it will only dismiss the keyboard. This means that the user always needs to tap twice in order to press anything on screen. This is especially troublesome if the UI has buttons to manage such input (for example to clear the text or just confirm the input).
In my case, I'm using it in a chat, and in order to send a message, the user needs to dismiss the keyboard first and then press the button to send the message, feels very buggy, but also in case they just want to exit the screen, they again need to tap twice.
I'm kind of surprise nobody has raised this issue before, looking at axmol code, seems it's just the way it was thought to be working, but UX wise is pretty bad.
Thanks in advance for reading this.
The text was updated successfully, but these errors were encountered:
erFra17
changed the title
TextField prevents receiving touches when in focus on iOS
TextField and GTextInput prevent receiving touches when in focus on iOS
Feb 17, 2025
I'm facing the same issues yep, I have a whole "onTouchBegan" event on the whole screen, but when I click on the screen, the first time it only dismiss the keyboard, and I need to re-click on the screen to actually trigger onTouchBegan
Axmol version: 2.1.0
Tested on iPhone SE, version 15.6.1
XCode 15.0.1
UPDATE: also the GTextInput from fairy does the same.
When a TextField is in focus, the GLView does not receive touches, hence, when tapping on a button (or anything else) it will only dismiss the keyboard. This means that the user always needs to tap twice in order to press anything on screen. This is especially troublesome if the UI has buttons to manage such input (for example to clear the text or just confirm the input).
In my case, I'm using it in a chat, and in order to send a message, the user needs to dismiss the keyboard first and then press the button to send the message, feels very buggy, but also in case they just want to exit the screen, they again need to tap twice.
I'm kind of surprise nobody has raised this issue before, looking at axmol code, seems it's just the way it was thought to be working, but UX wise is pretty bad.
Thanks in advance for reading this.
The text was updated successfully, but these errors were encountered: