> You could always just store the corresponding characters, then use char_to_button_id to get the appropriate id for the system you're on.
> This is useful when developing key configuration programs, or if you want your instructions to dynamically tell peopole what actual keys they should press (rather than just writing the static text "use WASD" and hoping they use QUERTY).
> That said, I think all "standard" buttons are going to be the same over every keyboard
display_name = Gosu::name_of_button(id)
return my_localization_replacements[display_name] || display_name
> since the keys will _always_ have the same physical position on the keyboard.
Powered by mwForum 2.29.0 © 1999-2013 Markus Wichitill