You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don't know if this is the right place for this issue.
Anyway.
It seems that Macro in current KLL spec treat the modifier key as the plain keys .
If I pressed one modifier key, let's say RShift, then trigger a macro with a LShift in it's result.
Do not release the RShift key.
at the end of macro it will send a LShift release event to host, which cause the "shift" flag changed on host. But the 'RShift' is still pressed.
The ideal way should be before macro execute, check the current modifier key status, if it's result contains a modifier key and that key has already active, than ignore the modifier key in result. let's user to release that modifier key manually.
I think this way is better.
The text was updated successfully, but these errors were encountered:
But what if you really wanted LShift not just "Shift"? And didn't care that RShift was being held.
This does make sense for the single quote macros though. Where you are trying to enter text. I'm thinking about changing how single quote macros work for KLL 0.6 anyways.
In that case, it should recover the modifier flag at the end of the macro result.
I'm holding shift, but the keyboard behave like I'm not. This is confusing.
I don't know if this is the right place for this issue.
Anyway.
It seems that Macro in current KLL spec treat the modifier key as the plain keys .
RShift
, then trigger a macro with aLShift
in it's result.RShift
key.LShift
release event to host, which cause the "shift" flag changed on host. But the 'RShift' is still pressed.The ideal way should be before macro execute, check the current modifier key status, if it's result contains a modifier key and that key has already active, than ignore the modifier key in result. let's user to release that modifier key manually.
I think this way is better.
The text was updated successfully, but these errors were encountered: