Key Up event is sometimes not detected when a heavy UI operation is ongoing

[TBM13]

Pressing the Windows key on FlowLauncher quickly and repeatedly while the settings window is opening can cause the hotkey to stop working until a different key is pressed.

Haven't looked much at the code but I'm guessing this is likely because the key up event is missed, so ChefKeys ignores subsequent Windows key presses until another one is pressed.

Also it's way easier to trigger this issue on Release mode, for whatever reason.

[jjw24]

Hey there, thanks for the issue report. Just to clarify the setting window you mentioned is that flow's settings window or Windows' settings?

I will see if I can reproduce when I get a chance.

[TBM13]

Flow's settings

[TBM13]

More details on the issue:

• I type settings in Flow's search bar and press enter on the result that opens Flow's settings
• Settings page starts loading. KEY_DOWN of enter is detected but not its KEY_UP
• Settings page finishes loading, but ChefKeys is already in a bugged state. If I press the open flow launcher hotkey (Windows key in my case), it thinks that I'm pressing the combination Enter + Windows key

There may be some differences since I heavily modified ChefKeys on my FlowLauncher fork, but more or less it should be something like that.