summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorQMK Bot <hello@qmk.fm>2021-12-27 02:57:38 +0000
committerQMK Bot <hello@qmk.fm>2021-12-27 02:57:38 +0000
commitdfe5fe718142db9eb19e1eda8f952ec7c726ea07 (patch)
treedf24720f271452fec7723ea89ee1a025a53eee7b
parentc20096c7aaa62618473b18bc2d7c08b68a48d14c (diff)
parentdb358d171d24eaa10286cbb72916302dd8e22d00 (diff)
downloadqmk_firmware-dfe5fe718142db9eb19e1eda8f952ec7c726ea07.tar.gz
qmk_firmware-dfe5fe718142db9eb19e1eda8f952ec7c726ea07.zip
Merge remote-tracking branch 'origin/master' into develop
-rw-r--r--docs/feature_macros.md2
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: