diff options
| author | Buttenup <50253991+Buttenup@users.noreply.github.com> | 2021-12-27 13:57:09 +1100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2021-12-27 13:57:09 +1100 |
| commit | db358d171d24eaa10286cbb72916302dd8e22d00 (patch) | |
| tree | 3b0138753320ef52c4b66af619d647dfd74093b5 | |
| parent | 2c8d46f40843507a4aff66368194faf25745fed9 (diff) | |
Update feature_macros.md (#15026)
* Update feature_macros.md
Added a link to the usage of SAFE_RANGE as this wasn't clear to me when I visited this page in isolation.
* Fix typo
Co-authored-by: Nick Brassel <nick@tzarc.org>
| -rw-r--r-- | docs/feature_macros.md | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/docs/feature_macros.md b/docs/feature_macros.md index 81ade58592..4368853569 100644 --- a/docs/feature_macros.md +++ b/docs/feature_macros.md @@ -144,6 +144,8 @@ If yes, we send the string `"QMK is the best thing ever!"` to the computer via t We return `true` to indicate to the caller that the key press we just processed should continue to be processed as normal (as we didn't replace or alter the functionality). Finally, we define the keymap so that the first button activates our macro and the second button is just an escape button. +?>It is recommended to use the SAFE_RANGE macro as per [Customizing Functionality](custom_quantum_functions.md). + You might want to add more than one macro. You can do that by adding another keycode and adding another case to the switch statement, like so: |