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
In key.js, the keys are currently hard coded to support japanese and us keyboard layouts, which seems a bit hacky to me. Whats the reason behind this?
If you use the keypress callback rather than keypress in eventhandler.js, you can get the actual typed char regardless of the keyboard layout with String.fromCharCode(e.which).
In my local installation of this plugin, I changed the key identifiers for de, so if String.fromCharCode(e.which) is no option in your opinion, maybe you could add those mappings:
In key.js, the keys are currently hard coded to support japanese and us keyboard layouts, which seems a bit hacky to me. Whats the reason behind this?
If you use the keypress callback rather than keypress in eventhandler.js, you can get the actual typed char regardless of the keyboard layout with String.fromCharCode(e.which).
In my local installation of this plugin, I changed the key identifiers for de, so if String.fromCharCode(e.which) is no option in your opinion, maybe you could add those mappings:
The text was updated successfully, but these errors were encountered: