diff options
| author | drashna <drashna@live.com> | 2017-11-06 17:43:38 +0100 |
|---|---|---|
| committer | Jack Humbert <jack.humb@gmail.com> | 2017-11-06 17:43:38 +0100 |
| commit | 2c703b1528a287b29817bd1129471e20743cfaa5 (patch) | |
| tree | 7a7cb7aaaea59c3fce42e00bc302037ff21262b8 /docs/feature_auto_shift.md | |
| parent | 90a6fea4e8aa5c2bb8f9e10dbb90cce78208d01d (diff) | |
| download | qmk_firmware-2c703b1528a287b29817bd1129471e20743cfaa5.tar.gz qmk_firmware-2c703b1528a287b29817bd1129471e20743cfaa5.tar.xz | |
Fix RGBLIGHT startup color (#1975)
* Fix RGBLIGHT startup color
While it's awesome to see the layer indicating code in here (no really!), and the general rule is to not alter the default keymap/code....
The problem with the layer_state_set_kb call handling this, is that the code doesn't seem to be called at startup. So the default layer color won't ever get set on startup. It needs to be called in the init function to be properly set.
I've played with this extensively, and if you check my keymaps, that is precisely why I have the setrgb/sethsv in the init function.
* Removed typo (pipe)
Diffstat (limited to 'docs/feature_auto_shift.md')
0 files changed, 0 insertions, 0 deletions