From 03de0c85754673500f4cee91e915743477c0d6f0 Mon Sep 17 00:00:00 2001 From: Daniel Gordon Date: Mon, 2 Oct 2017 07:03:40 -0500 Subject: [PATCH] Reference to rules.mk in tap dance docs added Change-Id: I64aa6f95a30ab05f0ed3f499e54b9e125d379fad --- docs/tap_dance.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/tap_dance.md b/docs/tap_dance.md index 38b2ee999..442162765 100644 --- a/docs/tap_dance.md +++ b/docs/tap_dance.md @@ -14,7 +14,7 @@ The implementation hooks into two parts of the system, to achieve this: into `pr But lets start with how to use it, first! -First, you will need `TAP_DANCE_ENABLE=yes` in your `Makefile`, because the feature is disabled by default. This adds a little less than 1k to the firmware size. Next, you will want to define some tap-dance keys, which is easiest to do with the `TD()` macro, that - similar to `F()`, takes a number, which will later be used as an index into the `tap_dance_actions` array. +First, you will need `TAP_DANCE_ENABLE=yes` in your `rules.mk`, because the feature is disabled by default. This adds a little less than 1k to the firmware size. Next, you will want to define some tap-dance keys, which is easiest to do with the `TD()` macro, that - similar to `F()`, takes a number, which will later be used as an index into the `tap_dance_actions` array. This array specifies what actions shall be taken when a tap-dance key is in action. Currently, there are three possible options: @@ -42,7 +42,7 @@ For the sake of flexibility, tap-dance actions can be either a pair of keycodes, Here's a simple example for a single definition: -1. In your `makefile`, add `TAP_DANCE_ENABLE = yes` +1. In your `rules.mk`, add `TAP_DANCE_ENABLE = yes` 2. In your `config.h` (which you can copy from `qmk_firmware/keyboards/planck/config.h` to your keymap directory), add `#define TAPPING_TERM 200` 3. In your `keymap.c` file, define the variables and definitions, then add to your keymap: