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
InputProcessor#keyTyped not fired for ESC, F1, F2, ... on Windows (not documented) #7304
Comments
So, This could probably be documented better, sure. A lot of things could. The main way you can tell if keyTyped will receive a char in its event handling is if that key would affect a TextField in some unambiguous way. That means So yeah. It's a can of worms, and it's not just our can. |
Issue details
I'm not sure if this is intended behaviour, but at the very least it should be documented:
keyUp
andkeyDown
are fired for special keys (escape, F1, ...etc) on my Windows machine, but notkeyTyped
.How do we know which keys will come in with keyTyped and not keyUp?
Reproduction steps/code
Typing in
h
,<backspace>
,<enter
>,<escape>
,<F1>
:Version of libGDX and/or relevant dependencies
Please select the affected platforms
The text was updated successfully, but these errors were encountered: