From f0957fd55ee1d8c5978a01263a392b12ba359590 Mon Sep 17 00:00:00 2001 From: drashna Date: Wed, 17 Aug 2022 02:38:35 +0000 Subject: [PATCH] =?UTF-8?q?Deploying=20to=20gh-pages=20from=20@=20qmk/qmk?= =?UTF-8?q?=5Ffirmware@a1f0208797a2dc241707e4ff3120f847187823c6=20?= =?UTF-8?q?=F0=9F=9A=80?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- feature_combo.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/feature_combo.md b/feature_combo.md index c0e10f09d5a..42d965509b9 100644 --- a/feature_combo.md +++ b/feature_combo.md @@ -326,7 +326,7 @@ bool process_combo_key_release(uint16_t combo_index, combo_t *combo, uint8_t key If you, for example, use multiple base layers for different key layouts, one for QWERTY, and another one for Colemak, you might want your combos to work from the same key positions on all layers. Defining the same combos again for another layout is redundant and takes more memory. The solution is to just check the keycodes from one layer. -With `#define COMBO_ONLY_FROM_LAYER _LAYER_A` the combos' keys are always checked from layer `_LAYER_A` even though the active layer would be `_LAYER_B`. +With `#define COMBO_ONLY_FROM_LAYER 0` in config.h, the combos' keys are always checked from layer `0`, even if other layers are active. ## User callbacks