diff options
author | Joel Challis <git@zvecr.com> | 2023-02-22 22:49:07 +0000 |
---|---|---|
committer | GitHub <noreply@github.com> | 2023-02-23 09:49:07 +1100 |
commit | 961f0b7b2de54f988daf4ce7b791f91a33e55612 (patch) | |
tree | a96aecd70d8f1341c81dc12d79cbb59a94803241 /docs | |
parent | ea772468650f7c79a9919a4770d371839985bef0 (diff) |
Reallocate SAFE_RANGE (#19909)
Diffstat (limited to 'docs')
-rw-r--r-- | docs/configurator_default_keymaps.md | 6 |
1 files changed, 2 insertions, 4 deletions
diff --git a/docs/configurator_default_keymaps.md b/docs/configurator_default_keymaps.md index ec74f4740c..4d3c1b8f47 100644 --- a/docs/configurator_default_keymaps.md +++ b/docs/configurator_default_keymaps.md @@ -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 |