Layer transparency

[dshields (Daniel Shields)]

I have replaced the function layer with two separate layers. Key transparency from the default layer to the first layer works as expected. Transparency from keys defined in the first layer to the second doesn’t work as I would expect. The second layer is getting keys from the default layer rather than the one below.

Is this behaviour expected?

[merlin (Michael Richters)]

If you share your .ino file, I’m pretty sure we can work out what’s gone wrong.

[algernon (Gergely Nagy)]

Transparency gets you keys from the active layers below. If you have three layers, with 0 and 2 active, transparent keys on layer 2 will be from layer 0. If you make layer 1 active too, then the transparent keys of layer 2 will be looked for on layer 1. If they are still transparent there, then from layer 0.

Does this clear things up a bit?

[dshields (Daniel Shields)]

That makes sense, I’ll adjust the key maps accordingly.

[Jennigma (Jennifer Leigh)]

Argh. This is the metaphor issue we were talking about here:

Multiple layers?

I agree that the wording doesn’t convey unambiguously. My metaphor for the keymaps is like a kids picture book with transparent overlay pages, but of course that fails because with a keymap stack you can apply each layer independently without the ones below it, while in a picture book if you are looking at layer 3 then layers 1 and 2 are also active. A metaphor of a stack of layers with toggle switches would more closely reflect the design than my picture book, so I see the merit of “Toggle.” …

I’ll adjust the intro document to be more correct right now. Might make sense to make a comment about this in the Model01-Firmware.ino as well. I am still not convinced that renaming the function names is the best course, but this behavior is going to confuse a lot of smart people, and we should think seriously about how to mitigate it.

[Jennigma (Jennifer Leigh)]

Improved section. Commentary welcome:

keyboardio/Kaleidoscope