You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, I am in search of a way to set up per key lighting per layer in the online configurator. I am getting into the hobby and I am wanting to create specific use case layers, but in order to really take advantage of the layers, I would like to assign specific lighting patterns for each layer. As I understand it now, the configurator does not currently support per key RGB, only RGB controls. I would have to edit the firmware files by hand before flashing to the board. Which would most likely end with a heavy brick, hahaha. If this is at all in the realm of possibility, a future feature like this would be a dream. Thank you!
The text was updated successfully, but these errors were encountered:
Functionality like this in QMK Configurator is a very long way off. There are a lot of underlying systems that would need changes to support something like this.
It may become a reality at some point, but I wouldn't hold my breath were I in your place.
You'd find your way faster learning how to compile QMK from source on your computer, and using the Lighting Layers feature, which was specifically written for the type of functionality you're after.
Description
Hello, I am in search of a way to set up per key lighting per layer in the online configurator. I am getting into the hobby and I am wanting to create specific use case layers, but in order to really take advantage of the layers, I would like to assign specific lighting patterns for each layer. As I understand it now, the configurator does not currently support per key RGB, only RGB controls. I would have to edit the firmware files by hand before flashing to the board. Which would most likely end with a heavy brick, hahaha. If this is at all in the realm of possibility, a future feature like this would be a dream. Thank you!
The text was updated successfully, but these errors were encountered: