Layering Simulation

[algernon]

Is your feature request related to a problem? Please describe.

When working with a keymap that has a number of transparent keys, it would be nice to be able to visually see what the transparent keys resolve to, given a particular active layer configuration.

For example, on my own keymap, my first two layers are "base layers" (Dvorak and Engram), with no transparent keys. I have two other layers which I use - Navigation and a Numpad/Hungarian layer -, which do use a set of transparent keys, mostly on the thumb arc. With Chrysalis, it is not immediately clear, nor very easy to discover what those keys resolve to: we have to go and view the other layer(s). The layer navigation box helps a little, as it shows what the currently selected key resolves to on other layers, but to see what the thumb arc resolves to, still requires me to click on all of those keys.

A better overview would be great.

Describe the solution you'd like

Of course, we can't passively show what transparent keys would resolve to, because that depends on what other layers we have active, and in which order, something we can't tell in advance. But we could make it possible to tell Chrysalis which layers are active, in what order, and then it could show the resolved transparent keys. Perhaps with a faded opacity, or some other indication that it isn't a key directly on the currently viewed layer.

This could be useful both for the layout editor, and the layout card screens, I believe.

[detzt]

Here's an idea for a solution that would cover all basic setups and many of the more advanced ones:

The user can select a base layer that is used as a reference and displayed as greyed-out labels on transparent keys.

• For the common setup of one base layer and multiple, independent, function layers this works perfectly.
• For another common setup of multiple, mutually exclusive, base layers (like qwerty and Dvorak) and function layers on top, this works in the best way I can imagine: The user can select Dvorak as base layer and get a preview of the function layers when coming from that layer. Then he can select qwerty as base layer and see how the function layers look like in that case.
  That is quite clear and I don't think it would be better to show the letters from Dvorak and qwerty at the same time on transparent keys.
• Same for OS-specific base layers.
• Setups with three or more partially transparent layers active at the same time are only partially supported as it can only look one layer deep. But I would argue that this is not a common setup and even this partial support helps more than only showing blank keys.