diff options
author | Drashna Jaelre <drashna@live.com> | 2018-10-10 12:38:10 -0700 |
---|---|---|
committer | Jack Humbert <jack.humb@gmail.com> | 2018-10-10 21:36:58 -0400 |
commit | a7d05820a6258178b7ea440ee2781edf074d8f41 (patch) | |
tree | 2940cffc57cd7e8854a33af5834aad2dbf217665 /docs/config_options.md | |
parent | 43757cd985153ba4f620336003c20b3554c03678 (diff) | |
download | qmk_firmware-a7d05820a6258178b7ea440ee2781edf074d8f41.tar.gz qmk_firmware-a7d05820a6258178b7ea440ee2781edf074d8f41.zip |
Add documentation for Combo feature
Diffstat (limited to 'docs/config_options.md')
-rw-r--r-- | docs/config_options.md | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/docs/config_options.md b/docs/config_options.md index 4678a7146c..19861c9d23 100644 --- a/docs/config_options.md +++ b/docs/config_options.md @@ -155,6 +155,10 @@ If you define these options you will enable the associated feature, which may in going to produce the 500 keystrokes a second needed to actually get more than a few ms of delay from this. But if you're doing chording on something with 3-4ms scan times? You probably want this. +* `#define COMBO_COUNT 2` + * Set this to the number of combos that you're using in the [Combo](feature_combo.md) feature. +* `#define COMBO_TERM 200` + * how long for the Combo keys to be detected. Defaults to `TAPPING_TERM` if not defined. ## RGB Light Configuration @@ -234,6 +238,8 @@ Use these to enable or disable building certain features. The more you have enab * Console for debug(+400) * `COMMAND_ENABLE` * Commands for debug and configuration +* `COMBO_ENABLE` + * Key combo feature * `NKRO_ENABLE` * USB N-Key Rollover - if this doesn't work, see here: https://github.com/tmk/tmk_keyboard/wiki/FAQ#nkro-doesnt-work * `AUDIO_ENABLE` |