A little while ago, on the path from firmware v11.x to firmware v12.x the key ids changed. It makes sense to use the text labels instead of the numeric ids.
As @kareltucek wrote, there may be additional bugs involved.
@kareltucek thanks for looking at it. I just turned the macros on again. I have them set on j , k , and l so it doesn’t matter which three I hit. And it works now! Without hitting the next layer buttons.
Sorry for your troubles. Maybe unplugging the keyboard in the last few days helped or restarting my computer. Thanks!
@maexxx amazing. I didn’t know there was an ‘or’ operator.
But when I simplify with the orGate operator it reintroduces the bug I was having.
I have vim arrow keys on my fn3, so when I’m in a word processor it inevitably hits one of the arrow keys after toggling the layer. Misplacing the cursor.
when I have it like this,
ifShortcut k l final toggleLayer fn3
ifShortcut l k final toggleLayer fn3
holdKey j
ifShortcut l j final toggleLayer fn3
ifShortcut j l final toggleLayer fn3
holdKey k
ifShortcut j k final toggleLayer fn3
ifShortcut k j final toggleLayer fn3
holdKey l
The anyOrder command doesn’t seem to work with three button presses.
After configuring the macro for the j , k, and l buttons I opened blank page in a word processor and pressed the three button’s ten times and got numerous misfires.