05-20-2007, 03:44 PM
Now I cannot analyze the code, test, etc, but only can say what I know so far.
Keyboard detector is incompatible with low level keyboard hooks when both run in the same process (in this case - QM). On my computers, low level hooks stop working. On somebody elses computer, LL hooks work but keyboard detector does not. Make sure that 'use low level keyboard hook' is unchecked in Options.
To work correctly, the WM_INPUT message (raw input) must be received before QM receives notification about the key through its keyboard hooks. Even if keyboard hooks work, low level hooks are always called before WM_INPUT. Non LL hooks in most cases are called after WM_INPUT.
What you described, happens when WM_INPUT is received later. On first message generated by new keyboard, QM still thinks that it came from old keyboard, because WM_INPUT for that key still did not arrived.
Keyboard detector is incompatible with low level keyboard hooks when both run in the same process (in this case - QM). On my computers, low level hooks stop working. On somebody elses computer, LL hooks work but keyboard detector does not. Make sure that 'use low level keyboard hook' is unchecked in Options.
To work correctly, the WM_INPUT message (raw input) must be received before QM receives notification about the key through its keyboard hooks. Even if keyboard hooks work, low level hooks are always called before WM_INPUT. Non LL hooks in most cases are called after WM_INPUT.
What you described, happens when WM_INPUT is received later. On first message generated by new keyboard, QM still thinks that it came from old keyboard, because WM_INPUT for that key still did not arrived.