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
Switching to another FlxState while a FlxInputText field is active causes a FlxInputTextManager to remain active and continue dispatching events when switching back to the original state. The code location of the error varies depending on how it's triggered, but it causes the app to access a null textField.
I have included a test app to reproduce the issue: Demo.zip
Steps
Run the app and click in the text field.
Press the "S" key to change to the next state while the text field is still active.
Press the "S" key to change back to the original state.
Upon pressing the Up or Down keys, or even clicking in the field again, the game will crash with a "Null access" error.
If we force the field to lose focus when destroying it, this issue no longer occurs.
The text was updated successfully, but these errors were encountered:
DigiEggz
added a commit
to DigiEggz/flixel
that referenced
this issue
Aug 21, 2024
Switching to another
FlxState
while aFlxInputText
field is active causes aFlxInputTextManager
to remain active and continue dispatching events when switching back to the original state. The code location of the error varies depending on how it's triggered, but it causes the app to access a nulltextField
.I have included a test app to reproduce the issue: Demo.zip
Steps
If we force the field to lose focus when destroying it, this issue no longer occurs.
The text was updated successfully, but these errors were encountered: