diff options
| author | Drashna Jaelre <drashna@live.com> | 2020-07-27 14:46:39 -0700 |
|---|---|---|
| committer | James Young <18669334+noroadsleft@users.noreply.github.com> | 2020-08-29 14:30:02 -0700 |
| commit | e6266b19be46c1340209bdd0a6c519452d5b9f2a (patch) | |
| tree | 7463f3c351623667b7d4aff956ab0c34a40ee4b5 /keyboards/paladin64/paladin64.c | |
| parent | 4b74f985ec7b14f5517df4e591f0c36b24f85f5c (diff) | |
| download | qmk_firmware-e6266b19be46c1340209bdd0a6c519452d5b9f2a.tar.gz qmk_firmware-e6266b19be46c1340209bdd0a6c519452d5b9f2a.zip | |
Initialize Layer State on startup (#8318)
* Initialize Layer State on startup
Right now, on startup, the default layer state gets called and set, triggering the callback functions for the default layer state. However, the normal layer state never actually gets initialized. It's set to 0 directly, by default, but the callback functions are never actually called. This creates some inconsistency in the behavior for end users. This adds a simple "clear" that triggers the callback on startup. This should produce more consisten behavior between the two functions and layer masks.
* Stupid hack
* Fix type casting?
* Fix compile issues with magic is disabled
Diffstat (limited to 'keyboards/paladin64/paladin64.c')
0 files changed, 0 insertions, 0 deletions