layer fn4 key i mapped to Keypress 8 * with modifier LShift.
layer base key rightSpace mapped to Keypress space with secondary action layer fn.
When pressing rightSpace+i quickly (and releasing quickly), the resulting keystroke is *. This is correct and expected behaviour. ✔️
Typing behaviour settings:
And in init macros:
set secondaryRole.advanced.acceptTriggersFromSameHalf false
set secondaryRole.advanced.minimumHoldTime 50
When the base key rightSpace is changed to run this macro:
numspace-micro:
ifPrimary acceptTriggersFromSameHalf final holdKey space
holdLayer fn4
Then pressing rightSpace+i quickly (and releasing quickly), the resulting keystroke is sometimes * and sometimes 8. This is wrong. ❌
The keystroke order is rightSpace press, i press, i release, rightSpace release, in quite quick timing. About half the time, the LShift modifier is lost.
The secondary layer activation from macro should not behave differently than when activated directly without macro.
Changing any of these timings does not change the behaviour:
In macro code:
In Agent:
- Timeout
- Double tap timeout
- Double tap to lock layer timeout
Changing init macros to set secondaryRole.advanced.acceptTriggersFromSameHalf true does not change the behaviour.
layer fn4 key
imapped to Keypress 8 * with modifier LShift.layer base key
rightSpacemapped to Keypress space with secondary action layer fn.When pressing
rightSpace+iquickly (and releasing quickly), the resulting keystroke is *. This is correct and expected behaviour. ✔️Typing behaviour settings:
And in init macros:
When the base key
rightSpaceis changed to run this macro:numspace-micro:
Then pressing
rightSpace+iquickly (and releasing quickly), the resulting keystroke is sometimes * and sometimes 8. This is wrong. ❌The keystroke order is
rightSpacepress,ipress,irelease,rightSpacerelease, in quite quick timing. About half the time, the LShift modifier is lost.The secondary layer activation from macro should not behave differently than when activated directly without macro.
Changing any of these timings does not change the behaviour:
In macro code:
In Agent:
Changing init macros to
set secondaryRole.advanced.acceptTriggersFromSameHalf truedoes not change the behaviour.