Great video, I learned a lot! I dug a bit into the QMK source code, and can offer some further context to the custom_keycodes enum. Deep in the builtin Quantum libraries a bunch of unique keycode IDs for unusual keys (music buttons, RGB, joysticks, pianos, etc.) are already defined, with "safe_range" being the last element. When you say "my_key1 = safe_range, my_key2, my_key3,..." that generates a sequence of unique keycode IDs (n,n+1,n+2,...) which starts counting from the end of that section, essentially appending your custom keycode IDs to the list of already known IDs. That way you can reference them the same as any other key and you're guaranteed not to have two key definitions overlap each other
Seems like RGBLIGHT_LIMIT_VAL corresponds to VALUE in HSV colour space. Is there any calculation we can perform to work out the theoretical total current load for n number of RGB LEDs in a KB? Is it something like "(RGBLIGHT_LIMIT_VAL / 255) * MAX_AMPS_PER_LED * n "? That assumes that the amps is linear with brightness, which is not the case. Like a 50% brightness will be < 50% current draw of the LED right?
Great video, I learned a lot! I dug a bit into the QMK source code, and can offer some further context to the custom_keycodes enum. Deep in the builtin Quantum libraries a bunch of unique keycode IDs for unusual keys (music buttons, RGB, joysticks, pianos, etc.) are already defined, with "safe_range" being the last element. When you say "my_key1 = safe_range, my_key2, my_key3,..." that generates a sequence of unique keycode IDs (n,n+1,n+2,...) which starts counting from the end of that section, essentially appending your custom keycode IDs to the list of already known IDs. That way you can reference them the same as any other key and you're guaranteed not to have two key definitions overlap each other
Always enjoy your enthusiasm and realistic comments. Keep going!
Seems like RGBLIGHT_LIMIT_VAL corresponds to VALUE in HSV colour space. Is there any calculation we can perform to work out the theoretical total current load for n number of RGB LEDs in a KB?
Is it something like "(RGBLIGHT_LIMIT_VAL / 255) * MAX_AMPS_PER_LED * n "? That assumes that the amps is linear with brightness, which is not the case. Like a 50% brightness will be < 50% current draw of the LED right?