summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorJez Cope <jezcope@users.noreply.github.com>2020-02-23 20:50:11 +0000
committerGitHub <noreply@github.com>2020-02-23 12:50:11 -0800
commit530c9976382a321d65c0339e0465932bd28f8cb9 (patch)
treec3cc970c09aa0c9e1c4692dbbdf05db1affed90d /docs
parentb353028ea5e0ac7b69e7fed4f224c7cb07015ec9 (diff)
downloadqmk_firmware-530c9976382a321d65c0339e0465932bd28f8cb9.tar.gz
qmk_firmware-530c9976382a321d65c0339e0465932bd28f8cb9.zip
Add link to "Useful functions" in macro docs (#7446)
* Add link to "Useful functions" in macro docs Help people find additional features they can activate within a macro * Update docs/feature_macros.md Co-Authored-By: Drashna Jaelre <drashna@live.com> Co-authored-by: skullydazed <skullydazed@users.noreply.github.com> Co-authored-by: Drashna Jaelre <drashna@live.com>
Diffstat (limited to 'docs')
-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 c13ae82061..7ca945683c 100644
--- a/docs/feature_macros.md
+++ b/docs/feature_macros.md
@@ -154,6 +154,8 @@ SEND_STRING(".."SS_TAP(X_END));
There are some functions you may find useful in macro-writing. Keep in mind that while you can write some fairly advanced code within a macro, if your functionality gets too complex you may want to define a custom keycode instead. Macros are meant to be simple.
+?> You can also use the functions described in [Useful function](ref_functions.md) for additional functionality. For example `reset_keyboard()` allows you to reset the keyboard as part of a macro.
+
### `record->event.pressed`
This is a boolean value that can be tested to see if the switch is being pressed or released. An example of this is