On the M01, I didn’t really need multiple layers, simply because there are more keys on the M01 and at most I mainly used the palm keys to temporarily shift to another layer for nav, media controls, misc keys, etc.
On the atreus, you have to use layer if you want to access numbers, punctuation, spacing, nav, modifiers, etc.
I’m trying to understand the difference between lock to layer vs move to layer. The shift to layer requires me to hold down the key to access layer-x. Where move to layer allows me to access that layer without holding down the move to layer key.
On a different note, I didn’t think I’d ever like any other kb as much as the M01, and I may not but I’m really liking the atreus. I backed one on faith that J and K put out marvelous things and ended up immediately getting a second one once I got to touch a real one.
Can we get an atreus 2 that has backlit keys?
Wasn’t sure where to put this or start a new thread but this thread seemed closest.
Oh, I just had a thought. atreus 3 can have morphing keys, the keycap itself is blank but the led below it will project the key corresponding to whatever layer you’ve activated… I know magic, may be too sci fi for some people. Dream big.
Mike R answered this question here:
@rloic already provided a link to the sketch, but I’ll answer your other question.
No, LockLayer() and MoveToLayer() are not equivalent. LockLayer(N) toggles the state of layer N when pressed, activating or deactivating that layer, but leaving all other layers unaffected. MoveToLayer(N) unconditionally activates layer N , and also deactivates all other layers (except the base layer).
The distinction matters because the layer stack is index-ordered. Layer N+1 is always above (and when active, its non-transparent keys will be masking) Layer N , regardless of the order in which they were activated. So, if both layers 2 and 3 are active, pressing LockLayer(2) will deactivate layer 2 , but would only affect the mapping of keys that are transparent on layer 3 . Pressing LockLayer(2) again would re-activate layer 2 , but layer 3 will still be the top layer. Pressing MoveToLayer(2) , however, will also deactivate layer 3 , and will result in layer 2 being active regardless of its previous status.