summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorwheredoesyourmindgo <moemanchu@icloud.com>2021-11-29 00:17:07 -0800
committerGitHub <noreply@github.com>2021-11-29 00:17:07 -0800
commit7f67504993f96936145a48f5cee7dcc1e2645a47 (patch)
tree7207835f736f3208affc051099a44eb5087787e0 /docs
parent4461355cce04750f021d0351939a35b1f7fdf5d5 (diff)
downloadqmk_firmware-7f67504993f96936145a48f5cee7dcc1e2645a47.tar.gz
qmk_firmware-7f67504993f96936145a48f5cee7dcc1e2645a47.zip
Added cancel_key_lock function (#15321)
Diffstat (limited to 'docs')
-rw-r--r--docs/feature_key_lock.md3
1 files changed, 2 insertions, 1 deletions
diff --git a/docs/feature_key_lock.md b/docs/feature_key_lock.md
index 8e6e29f0e6..7681394229 100644
--- a/docs/feature_key_lock.md
+++ b/docs/feature_key_lock.md
@@ -19,4 +19,5 @@ First, enable Key Lock by setting `KEY_LOCK_ENABLE = yes` in your `rules.mk`. Th
Key Lock is only able to hold standard action keys and [One Shot modifier](one_shot_keys.md) keys (for example, if you have your Shift defined as `OSM(KC_LSFT)`).
This does not include any of the QMK special functions (except One Shot modifiers), or shifted versions of keys such as `KC_LPRN`. If it's in the [Basic Keycodes](keycodes_basic.md) list, it can be held.
-Switching layers will not cancel the Key Lock.
+Switching layers will not cancel the Key Lock. The Key Lock can be cancelled by calling the `cancel_key_lock()` function.
+