diff options
| author | QMK Bot <hello@qmk.fm> | 2022-08-17 02:37:10 +0000 |
|---|---|---|
| committer | QMK Bot <hello@qmk.fm> | 2022-08-17 02:37:10 +0000 |
| commit | cfab3e2d6eb7d13ac940bcc46d5ab2880b46effc (patch) | |
| tree | afa2436250e046d07f14acff556ee0d1bd3db18f /docs | |
| parent | 77150d00acf12060cc1b31bcb978750d831910c6 (diff) | |
| parent | a1f0208797a2dc241707e4ff3120f847187823c6 (diff) | |
| download | qmk_firmware-cfab3e2d6eb7d13ac940bcc46d5ab2880b46effc.tar.gz qmk_firmware-cfab3e2d6eb7d13ac940bcc46d5ab2880b46effc.zip | |
Merge remote-tracking branch 'origin/master' into develop
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/feature_combo.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/feature_combo.md b/docs/feature_combo.md index c0e10f09d5..42d965509b 100644 --- a/docs/feature_combo.md +++ b/docs/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 |