My device (Asus G513QM) has certain keys with multiple LEDs under one key. Is there a possibility of being able to set up a reference for one LED to use the value of another LED, to have all the LEDs on one key effectively share the value of the main key?
For example, the space bar on this laptop is represented by the following four LED IDs; LedID.KeyboardCustom58, LedID.KeyboardCustom59, LedId.Keyboard_Space, and LedID.KeyboardCustom60. I would like to be able to reference the value being sent to LedId.Keyboard_Space and apply that to the other three LEDs, whether that be via a data model or via other means. The problem is that I may not always want to associate the keys in this manner; for example, I would want this to apply in a Chroma integration to make all four LEDs consistent to the one key, but not if I was running a gradient across the keyboard. Hence, a data model would likely be the preferred implementation, as it can be applied at the profile-level. The downsides of this approach may include the ability to recursively select a value, causing an infinite loop and/or memory requirements ballooning; as well as the timeframe to calculate the data model values expanding beyond the core framerate of the application.
I have attached a couple of videos showing the usecase for this in diogotr7/Artemis.Plugins#26.
My device (Asus G513QM) has certain keys with multiple LEDs under one key. Is there a possibility of being able to set up a reference for one LED to use the value of another LED, to have all the LEDs on one key effectively share the value of the main key?
For example, the space bar on this laptop is represented by the following four LED IDs; LedID.KeyboardCustom58, LedID.KeyboardCustom59, LedId.Keyboard_Space, and LedID.KeyboardCustom60. I would like to be able to reference the value being sent to LedId.Keyboard_Space and apply that to the other three LEDs, whether that be via a data model or via other means. The problem is that I may not always want to associate the keys in this manner; for example, I would want this to apply in a Chroma integration to make all four LEDs consistent to the one key, but not if I was running a gradient across the keyboard. Hence, a data model would likely be the preferred implementation, as it can be applied at the profile-level. The downsides of this approach may include the ability to recursively select a value, causing an infinite loop and/or memory requirements ballooning; as well as the timeframe to calculate the data model values expanding beyond the core framerate of the application.
I have attached a couple of videos showing the usecase for this in diogotr7/Artemis.Plugins#26.