diff options
| author | QMK Bot <hello@qmk.fm> | 2021-02-28 05:42:46 +0000 |
|---|---|---|
| committer | QMK Bot <hello@qmk.fm> | 2021-02-28 05:42:46 +0000 |
| commit | 85dd0556d739df23fa14b071a1af155eeef70b83 (patch) | |
| tree | 133320fcab2b7cafdf07a4ab45c9595191d14d8e /docs/feature_macros.md | |
| parent | e86e7c351df36634b1ca0d29c8453e4d527b73a4 (diff) | |
| parent | 2395069b0bf84e2667c36460d5c3a3c4225cbd85 (diff) | |
Merge remote-tracking branch 'origin/master' into develop
Diffstat (limited to 'docs/feature_macros.md')
| -rw-r--r-- | docs/feature_macros.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/feature_macros.md b/docs/feature_macros.md index 6e69ad642c..3660f37755 100644 --- a/docs/feature_macros.md +++ b/docs/feature_macros.md @@ -209,7 +209,7 @@ 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 functions](ref_functions.md) for additional functionality. For example `reset_keyboard()` allows you to reset the keyboard as part of a macro. +?> You can also use the functions described in [Useful function](ref_functions.md) and [Checking modifier state](feature_advanced_keycodes#checking-modifier-state) for additional functionality. For example, `reset_keyboard()` allows you to reset the keyboard as part of a macro and `get_mods() & MOD_MASK_SHIFT` lets you check for the existence of active shift modifiers. ### `record->event.pressed` |