Open philtherobot opened 1 year ago
If you're using one of the latest commits (or the latest release), there should be no queueing save the system hotkey queue itself. Are you using a key mapped (VK or SC) or a state mapped (e.g., eD) layout?
I have a copy of the repo I made on January 25th, compiled it, and this is my layout:
[pkl]
layout = QWERTY\QWE-eD_ANS:QWERTY-eD (ANS) ; Generated by the EPKL LayoutPicker UI, 2023-01-25_10-02
Unless you need the AltGr mappings, use a VK/SC (or eD2VK) layout instead. It might help a little.
You aren't using any other scripts that use a low-level keyboard hook (AHK or otherwise), are you?
When my computer is under heavy load, sometimes typing the letters "t" "h" "i" and "s" (in this order) will get printed as "s" "i" "h" and "t", in this exact reversed order.
"Heavy load" means a large program compilation job with multiple processes totaling more threads than there are actual cores. The computer is generally usable, other programs will load, Teams and Chrome work, but a bit sluggish. So "heavy" but not "excessive" to the point the computer is locked up.
I suspect AutoHotKey has an internal queue that it does not necessarily process in FIFO order. But I know nothing about the implementation, still it is a way to describe what's happening.