Andreas,
You obviously changed a heck of a lot more than just winProcessKeyEvent is
only defined when WIN_NEW_KEYBOARD_SUPPORT is YES (while it is NO by default
and basically comments out an incomplete experimental feature so that I
could make a release). However, you call the other version of
Andreas,
Interesting. I think you may have found the reason (and solution) for
why a select few users with non-U.S. keyboard layouts are still having
problems with fake Control_L presses and releases.
I appreciate the FSM state transition table, but could you give me a few
sentences
Hi Harold,
the FSM is doing something like a lookahead. This lookahead is only
done when the first Control_L press is detected.
Normally the FSM stays in the initial state 0 and passes all input
through. So there is no real transformation.
But if the FSM detects a Control_L press it keeps this
