Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(parser): add optional display-name to layer #20

Merged
merged 1 commit into from
Jan 9, 2024
Merged

feat(parser): add optional display-name to layer #20

merged 1 commit into from
Jan 9, 2024

Conversation

huber-th
Copy link
Contributor

@huber-th huber-th commented Dec 15, 2023

My keymap was failing with sub-expression Layer+ must match at least once. Turns out it was because I have a label assigned to each layer in my keymap which is used in ZMK to show the current layer on displays via widget.

My keymap layers start like this

default_layer {
    label = "Base";
    bindings = <

This change adds support for an optional label property in layers which can match zero or once. Potentially the label could be used to print on the images in the top left corner rather than the layer identifier of the keymap.

See zmkfirmware/zmk#551 which is the merged change in ZMK to support using the label to show in display widgets. There is also zmkfirmware/zmk#578 which is to document this optional layer.

Add support for an optional label property in layers
which can match zero or once.

In ZMK each layer can be assigned a display-name. One use case for
the label is that it can be shown in display widgets.

See zmkfirmware/zmk#551
@huber-th
Copy link
Contributor Author

huber-th commented Jan 8, 2024

It was announced on the ZMK discord that label will change to display-name. Updated the branch to refer to display-name instead of label.

Discord message announcing the change

@huber-th huber-th changed the title feat(parser): add optional label to layer feat(parser): add optional display-name to layer Jan 8, 2024
@MrMarble MrMarble merged commit f7d96b1 into MrMarble:master Jan 9, 2024
@MrMarble
Copy link
Owner

MrMarble commented Jan 9, 2024

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants