aboutsummaryrefslogtreecommitdiff
path: root/docs/feature_rgblight.md
diff options
context:
space:
mode:
authorQMK Bot <[email protected]>2023-11-03 23:14:49 +0000
committerQMK Bot <[email protected]>2023-11-03 23:14:49 +0000
commitc9afacccf437d6bd2921496b80e26afdd110c417 (patch)
treedd2ef04c28875c84fe9e8311936838daf700cbbe /docs/feature_rgblight.md
parentc6bb5b67559fa227fc15f00bfd6dc0c2e6bf1d7a (diff)
parentace510ffa0f8d51e1393ae9fcd17da00a5404c37 (diff)
downloadqmk_firmware-c9afacccf437d6bd2921496b80e26afdd110c417.tar.gz
qmk_firmware-c9afacccf437d6bd2921496b80e26afdd110c417.zip
Merge remote-tracking branch 'origin/master' into develop
Diffstat (limited to 'docs/feature_rgblight.md')
-rw-r--r--docs/feature_rgblight.md5
1 files changed, 2 insertions, 3 deletions
diff --git a/docs/feature_rgblight.md b/docs/feature_rgblight.md
index 2db878eb5f..8a64454b0d 100644
--- a/docs/feature_rgblight.md
+++ b/docs/feature_rgblight.md
@@ -525,7 +525,6 @@ By defining `RGBLIGHT_LED_MAP` as in the example below, you can specify the LED
```
<img src="https://user-images.githubusercontent.com/2170248/55743725-08ad7a80-5a6e-11e9-83ed-126a2b0209fc.JPG" alt="simple mapped" width="50%"/>
-```
## Clipping Range
Using the `rgblight_set_clipping_range()` function, you can prepare more buffers than the actual number of LEDs, and output some of the buffers to the LEDs. This is useful if you want the split keyboard to treat left and right LEDs as logically contiguous.
@@ -545,8 +544,8 @@ In addition to setting the Clipping Range, you can use `RGBLIGHT_LED_MAP` togeth
#define RGBLED_NUM 8
#define RGBLIGHT_LED_MAP { 7, 6, 5, 4, 3, 2, 1, 0 }
-// some soruce
- rgblight_set_clipping_range(3, 4);
+// some source
+rgblight_set_clipping_range(3, 4);
```
<img src="https://user-images.githubusercontent.com/2170248/55743747-119e4c00-5a6e-11e9-91e5-013203ffae8a.JPG" alt="clip mapped" width="70%"/>