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

RGB layer indicator #2

Open
MattSturgeon opened this issue Sep 20, 2023 · 4 comments
Open

RGB layer indicator #2

MattSturgeon opened this issue Sep 20, 2023 · 4 comments

Comments

@MattSturgeon
Copy link
Owner

Not sure if this is currently possible with ZMK and the Glove80, but it'd be nice to have some conditional lighting to indicate when a special layer is active.

@MattSturgeon
Copy link
Owner Author

Per key RGB support is tracked here: zmkfirmware/zmk#554
Whole board lighting is apparently supported.

Maybe look into if this is what the RGB keys on the Magic layer use? Might be able to use that for now?

@MattSturgeon
Copy link
Owner Author

MattSturgeon commented Mar 31, 2024

Someone got this working by patching the actual zmk firmware: diff here

TLDR;

Patch zmk_led_write_pixels in rgb_underglow.c;

Set pixels[key_index] to some HEXRGB struct, if zmk_keymap_layer_active(layer_id) is true.

@steynh
Copy link

steynh commented May 23, 2024

I think in general it would be really useful if we could specify an RGB grid for each layer. That way it becomes possible to visually highlight groups of keys (such as a numpad block) in different layers. And then it also becomes very obvious which layer is active. Both of these would be so helpful when just getting used to a new layout.

Animations are cool to have, but they seem quite complex to implement. Whereas just a simple grid per layer seems relatively simple to implement and actually offers a lot of practical benefits.

@adambiggs
Copy link

That would be perfect!

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

No branches or pull requests

3 participants