InputScope logs non-existent and not used key combos

[Quake4Life]

There's no way I pressed Ctrl+Backspace or AltGr+Enter or any like those

[suurjaak]

What may have happened, is that you e.g. pressed Ctrl and then Backspace, rapidly enough after each other that the operating system did not signal Ctrl being released, before Backspace got signaled as being pressed down.

Tested this a bit; when I press Backspace very quickly after Ctrl, the event signaling the release of Ctrl does sometimes actually arrive after Backspace.

Not sure if there is anything to do about this.

[Quake4Life]

Is there any way to register after a slightly longer time period? Combos are my fav statistics actually. But they seem broken to me now :( пт, 12 апр. 2024 г. в 17:27, Erki Suurjaak ***@***.***>:

…

What may have happened, is that you e.g. pressed Ctrl and then Backspace, rapidly enough after each other that the operating system did not signal Ctrl being released, before Backspace got signaled as being pressed down. Tested this a bit; when I press Backspace very quickly after Ctrl, the event signaling the release of Ctrl does sometimes actually arrive after Backspace. Not sure if there is anything to do about this. — Reply to this email directly, view it on GitHub <#31 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A44HBPTZF3HVOID6AR5IL7TY47VMHAVCNFSM6AAAAABGCXYEG6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANJRHA3DOMRYGM> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[suurjaak]

At the moment I can't really see how to differentiate between a legit combo and an inadvertent one. The keyboard events arrive as they do, and a legit combo may get released equally rapidly.

[suurjaak]

@Quake4Life Do you think there is anything that can be done with this issue?

[Quake4Life]

If there is no way to set "active window" in milliseconds after which combo is no longer registered, unfortunately, no ср, 24 апр. 2024 г., 12:06 Erki Suurjaak ***@***.***>:

…

@Quake4Life <https://github.com/Quake4Life> Do you think there is anything that can be done with this issue? — Reply to this email directly, view it on GitHub <#31 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A44HBPUAM2IXLYPQMHCVUADY65YXXAVCNFSM6AAAAABGCXYEG6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANZUGQ3DANBQGE> . You are receiving this because you were mentioned.Message ID: ***@***.***>