aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorGravatar hmkemppainen <github@guu.fi>2019-12-08 04:18:05 +0200
committerGravatar Joel Challis <git@zvecr.com>2019-12-08 02:18:05 +0000
commite676278474b853fb16187e605c037930c4927144 (patch)
tree07abe83ffe208a48b2447b4594921e495a90f68c
parent730a736ef049832988e1dc28228cd1d692d359f0 (diff)
downloadqmk_firmware-e676278474b853fb16187e605c037930c4927144.tar.gz
fix instructions for oneshot layer handling on key release (#7554)
* fix instructions for oneshot layer handling on key release * use ONESHOT_OTHER_KEY_PRESSED instead of ONESHOT_PRESSED Co-Authored-By: Drashna Jaelre <drashna@live.com>
-rw-r--r--docs/feature_advanced_keycodes.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/feature_advanced_keycodes.md b/docs/feature_advanced_keycodes.md
index e73258d51..ec3807f40 100644
--- a/docs/feature_advanced_keycodes.md
+++ b/docs/feature_advanced_keycodes.md
@@ -155,7 +155,7 @@ You can control the behavior of one shot keys by defining these in `config.h`:
Sometimes, you want to activate a one-shot key as part of a macro or tap dance routine.
-For one shot layers, you need to call `set_oneshot_layer(LAYER, ONESHOT_START)` on key down, and `set_oneshot_layer(ONESHOT_PRESSED)` on key up. If you want to cancel the oneshot, call `reset_oneshot_layer()`.
+For one shot layers, you need to call `set_oneshot_layer(LAYER, ONESHOT_START)` on key down, and `clear_oneshot_layer_state(ONESHOT_OTHER_KEY_PRESSED)` on key up. If you want to cancel the oneshot, call `reset_oneshot_layer()`.
For one shot mods, you need to call `set_oneshot_mods(MOD)` to set it, or `clear_oneshot_mods()` to cancel it.