properly drawing ISO/BAE enter key?

[zackforbing]

I found the keymap layout helper app (which could be more easily discoverable!), but I'm attempting to model an ISO enter, and it doesn't seem that there is a way to show the "step", it only reads x/h/w and not x2/h2/w2, which is how the secondary "step" is denoted. is there a way I'm missing to model keys like this in .json?

I currently just model two separate keys occupying the same row/col with the larger one on top:

...
{ "row": 3, "col": 8, "x":   8.5, "y":    3, "w":  1.5, "h": 1 },
{ "row": 3, "col": 8, "x":  8.75, "y":    3, "w": 1.25, "h": 2, "2h": 1 }
...

but this throws an error on opening the layout in Keymap Editor.

[nickcoutsos]

It doesn't exist currently. I mocked something up a while ago but it relies on CSS clipping which has other effects that made me unhappy.

x2/h2/w2, which is how the secondary "step" is denoted

I haven't heard of this, it's not something I support and it doesn't seem to be specified in QMK's layout format either.

[zackforbing]

it wasn't QMK's format, but keyboard-layout-editor's format. QMK wouldn't really have a need for those designations, IMO, since it isn't making a graphical representation of the keys at any point, really.

looking at the default ISO 60% kle, if you click the raw data tab, you can see those fields in use for the enter key.

[nickcoutsos]

Ah, ok. QMK based the layout format for QMK configurator on KLE but more clearly defined, which is why I base my format on theirs.

[nickcoutsos]

I pulled up my old branch to play around with:

There are some issues as I mentioned earlier due to the ISO Enter shape being a purely cosmetic styling, while the geometry is still treated as a 1.5x2 rectangle.

This means that the overlap check (a warning specific to the helper app) and drag selections are going to trigger in situations where you're in that region but not over the actual key polygon. That's a fairly small space so it shouldn't interfere too badly with regular use.

It also means that any border styling I want to apply is cut off. In the helper app that's a small annoyance since it's a visual cue for pending key selection. In keymap editor this isn't a factor because none of the key styles (as far as I recall) use borders, but if I were to go forward with this it would likely nag at me.