ok. been messing with it for a little.
this is how he is trying to use "layer toggle"
- on layer0 (we'll pick "Home") and make it "T1"
- on layer1 we'll change "Home" to "T2"
- on layer2 we'll change "Home" to "T3"
- etc...
using "layer toggle" will ascend the layers: layer0 > layer1 > layer2, etc...
or skip to a higher layer: layer2 > layer5
but does not want to descend layers: layer3 > layer2
or skip to a lower layer: layer5 > layer1
in this configuration.
because it is not meant to be used this way.
"layer toggle" is meant to ACTIVATE a layer, then tapping the same key again to DEACTIVATE the layer and go back to the layer you were on previously.
how it's meant to function:
- on layer0 (we'll pick "Home" again) and make it T3
- we tap on "Home" to TOGGLE ON layer3, then we can use the keymap for layer3
- we tap on "Home" again to TOGGLE OFF layer3 and are now back to layer0
i really think the dual role "action_layer_tap_key" is your best option to momentarily (while holding key) access a layer without having a bunch of dedicated layer toggles.
the way "action_layer_tap_key" functions is:
- on layer0 (we'll pick "Home" again) and make it "action_layer_tap_key", "Home", "layer1"
- when you TAP "Home" you get "Home"
- when you HOLD "Home" you get access to layer1
see below:
TMK layer switching descriptions
https://github.com/tmk/tmk_keyboard/blob/master/tmk_core/doc/keymap.md#3-layer-switching-example