drashna/qmk_firmware
1
0
Fork 0
Code Activity Actions

Reallocate SAFE_RANGE (#19909)

Browse source
This commit is contained in:
Joel Challis 2023-02-22 22:49:07 +00:00 • committed by GitHub
parent ea77246865
commit 961f0b7b2d
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
50 changed files with 31 additions and 132 deletions
Download patch file Download diff file Expand all files Collapse all files

6
docs/configurator_default_keymaps.md
View file

@ -153,10 +153,9 @@ bool process_record_user(uint16_t keycode, keyrecord_t *record) {
```c
enum keyboard_keycodes {
CUSTOM_1 = SAFE_RANGE,
CUSTOM_1 = QK_KB_0,
CUSTOM_2,
CUSTOM_3,
NEW_SAFE_RANGE // Important!
};
```
@ -185,8 +184,7 @@ bool process_record_kb(uint16_t keycode, keyrecord_t *record) {
};
```
Note the call to `process_record_user()` at the end. Additionally, users of the keyboard will need to use `NEW_SAFE_RANGE` instead of `SAFE_RANGE` if they wish to add their own custom keycodes at keymap level, beyond what is provided by the keyboard.
Note the call to `process_record_user()` at the end.
## Additional Reading :id=additional-reading