diff options
| author | QMK Bot <hello@qmk.fm> | 2022-02-27 02:39:15 +0000 |
|---|---|---|
| committer | QMK Bot <hello@qmk.fm> | 2022-02-27 02:39:15 +0000 |
| commit | cb8528c33cafbd609a19ddc749a6c2eb4e611992 (patch) | |
| tree | c5c67ca53b1017d2741594aeb4c0b06f4f0baa80 | |
| parent | d9a69324c18a0e4bdad68b82a948d5404948e414 (diff) | |
| parent | 29ab430f1f302bc64ad1549147f24235ba230a9c (diff) | |
Merge remote-tracking branch 'origin/master' into develop
| -rw-r--r-- | docs/feature_rgb_matrix.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/feature_rgb_matrix.md b/docs/feature_rgb_matrix.md index e2312f2766..87dbc5f780 100644 --- a/docs/feature_rgb_matrix.md +++ b/docs/feature_rgb_matrix.md @@ -528,7 +528,7 @@ All RGB keycodes are currently shared with the RGBLIGHT system: `RGB_MODE_PLAIN`, `RGB_MODE_BREATHE`, `RGB_MODE_RAINBOW`, and `RGB_MODE_SWIRL` are the only ones that are mapped properly. The rest don't have a direct equivalent, and are not mapped. -?> `RGB_*` keycodes cannot be used with functions like `tap_code16(RGB_HUD)` as they're not USB HID keycodes. If you wish to replicate similar behaviour in custom code within your firmware (e.g. inside `encoder_update_user()` or `process_record_user()`), the equivalent [RGB functions](#functions-idfunctions) should be used instead. +?> `RGB_*` keycodes cannot be used with functions like `tap_code16(RGB_HUD)` as they're not USB HID keycodes. If you wish to replicate similar behaviour in custom code within your firmware (e.g. inside `encoder_update_user()` or `process_record_user()`), the equivalent [RGB functions](#functions) should be used instead. !> By default, if you have both the [RGB Light](feature_rgblight.md) and the RGB Matrix feature enabled, these keycodes will work for both features, at the same time. You can disable the keycode functionality by defining the `*_DISABLE_KEYCODES` option for the specific feature. |