Eli Zaretskii wrote:
A slightly simplified version of the hook function I use is found
below. As you can see from the code most keyboard input just passes
by this hook.
Your hook assumes that when you see, e.g., VK_RWIN, it is the actual
keypress of the RightWindow key. But in a low-level hook, this
assumption might well be wrong, because the key could have been
preceded by some modifier,
Could you explain what you mean? I have noticed no problem of this kind.
during the years I have been using this. As far as I know if VK_RWIN is
found in the low level keyboard hook, then it is the RightWindows key
that has been pressed. Always.
But maybe you know something I am not aware of about this?
or even remapped by higher-level hooks to
something else.
I do not get this. The low level hook is the first hook of any kind to
see the keyboard events.
(Btw, your handler lacks the default: case.)
Nothing should be done in the default case. Is there any need for
"default:" then? (Ie it should be handled the default way in Windows and
that is what happens.)
That is why I say that it does not raise the complexity for that
input.
And that is why I say it does.
Maybe I will understand if you explain above.
