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
TetaNES allows fully customizing all keybindings, but it may be confusing to users with custom keyboard layouts to lookup the controls in the README, only to discover that the default key bindings don't match their layout.
Normally for games, physical_key can be useful like WASD for movement so the best path forward may be to support both and rely on physical_key for the default keyboard bindings for Player 1, and logical_key for all other bindings.
The text was updated successfully, but these errors were encountered:
Winit docs outline the differences pretty well: https://docs.rs/winit/latest/winit/event/struct.KeyEvent.html#structfield.physical_key
TetaNES allows fully customizing all keybindings, but it may be confusing to users with custom keyboard layouts to lookup the controls in the README, only to discover that the default key bindings don't match their layout.
Normally for games,
physical_key
can be useful like WASD for movement so the best path forward may be to support both and rely on physical_key for the default keyboard bindings for Player 1, and logical_key for all other bindings.The text was updated successfully, but these errors were encountered: