Repository navigation
No F1 or Fx input #3
Description
Activity
@shiguowang That should be simple enough. I will take a look at it tonight. 🙌
@shiguowang Sorry for the delay. I merged this PR #4 . Are you on windows or Mac? I also updated docs so that people run
git submodule update --init --recursiveafter they add submodules to load dependencies properly.It looks like the library is missing key event bindings for F1 and F2. Could you clarify if you're trying to implement this functionality in a specific module or if there's a preferred method for handling key inputs that we should adhere to?
Could you specify if you're trying to add the F1 and F2 bindings in the
key_input_handler.pymodule, or if you're looking to implement them in a different context? This would help determine whether we need to create new functions for these key events or modify existing ones.If we follow the pattern in
key_input_handler.py, we should check if the existing key-code mapping object needs a new entry for the virtual key constants VK_F1 and VK_F2. Does the current event listener implementation support these function keys, or do we need to add a specific case to the switch statement handling the event object's key property?The existing
KEY_MAPdictionary inkey_input_handler.pyrelies on standard ASCII mappings which do not account for function keys. We should define the virtual key constants for F1 through F12 and update the_process_eventmethod to handle these as non-character input events. Before modifying the event loop, does the underlying input backend currently capture extended key codes, or will we need to add a translation layer to map these virtual keys to the existing event dispatcher?
This is a clear libray, please add input keyboard "F1"/"F2"