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
(This is actually a minor bug, but a bigger enhancement request...) If a numpad keycode, KEY_KP_* is encountered, it causes the error Invalid get index 'Kp...' (on base: 'Dictionary') because the KEY_KP_ entries are missing from the _KEYS array. Quick fix is to add those to _KEYS, however this just leads to an empty texture. That can also be addressed (one way is to parse out the "Kp " before looking for the texture), but it leads to a bigger question. How can the UI differentiate between numpad keys and their non-numpad equivalents?
Is there some way I missed to handle this?
If I haven't missed something, I imagine two possibilities. Show two textures for numpad keys (numlock and the key), or use a color to differentiate (red is already used in the high-res Kenney icons, so this seems reasonable).
The meaning of the red color for numpad keys might be explained by adding a keyboard representation colored the same way (for example, imagine extending the keyboard below with a red keypad)
(Keyboard is from openclipart.org, the rest is from Kenney's)
What do you think? Have you dealt with this a different way?
Contribution Request
Yes
Additional Notes (Optional)
No response
The text was updated successfully, but these errors were encountered:
Feature Description
(This is actually a minor bug, but a bigger enhancement request...) If a numpad keycode,
KEY_KP_*
is encountered, it causes the errorInvalid get index 'Kp...' (on base: 'Dictionary')
because theKEY_KP_
entries are missing from the_KEYS
array. Quick fix is to add those to_KEYS
, however this just leads to an empty texture. That can also be addressed (one way is to parse out the "Kp " before looking for the texture), but it leads to a bigger question. How can the UI differentiate between numpad keys and their non-numpad equivalents?Is there some way I missed to handle this?
If I haven't missed something, I imagine two possibilities. Show two textures for numpad keys (numlock and the key), or use a color to differentiate (red is already used in the high-res Kenney icons, so this seems reasonable).
The meaning of the red color for numpad keys might be explained by adding a keyboard representation colored the same way (for example, imagine extending the keyboard below with a red keypad)
(Keyboard is from openclipart.org, the rest is from Kenney's)
What do you think? Have you dealt with this a different way?
Contribution Request
Yes
Additional Notes (Optional)
No response
The text was updated successfully, but these errors were encountered: