clarified tap
parent
1bff72c009
commit
66e9cf9718
|
@ -6,6 +6,7 @@
|
|||
#include "quantum.h"
|
||||
|
||||
#define _______ KC_TRNS
|
||||
#define EMOJIBLOCK 5
|
||||
|
||||
|
||||
//declarations for tap dancing emojis
|
||||
|
@ -189,7 +190,7 @@ void cycleEmojis(qk_tap_dance_state_t *state, void *user_data) {
|
|||
register_hex32(pgm_read_dword(&unicode_map[state->count]));
|
||||
unicode_input_finish();
|
||||
}
|
||||
else if(state->count <= 5) {
|
||||
else if(state->count <= EMOJIBLOCK) {
|
||||
tap(KC_BSPC);
|
||||
unicode_input_start();
|
||||
register_hex32(pgm_read_dword(&unicode_map[state->count]));
|
||||
|
@ -203,7 +204,7 @@ void cycleAnimals(qk_tap_dance_state_t *state, void *user_data) {
|
|||
register_hex32(pgm_read_dword(&unicode_map[state->count+5]));
|
||||
unicode_input_finish();
|
||||
}
|
||||
else if(state->count <= 5) {
|
||||
else if(state->count <= EMOJIBLOCK) {
|
||||
tap(KC_BSPC);
|
||||
unicode_input_start();
|
||||
register_hex32(pgm_read_dword(&unicode_map[state->count+5]));
|
||||
|
@ -217,7 +218,7 @@ void cycleHands(qk_tap_dance_state_t *state, void *user_data) {
|
|||
register_hex32(pgm_read_dword(&unicode_map[state->count+10]));
|
||||
unicode_input_finish();
|
||||
}
|
||||
else if(state->count <= 5) {
|
||||
else if(state->count <= EMOJIBLOCK) {
|
||||
tap(KC_BSPC);
|
||||
unicode_input_start();
|
||||
register_hex32(pgm_read_dword(&unicode_map[state->count+10]));
|
||||
|
@ -231,7 +232,7 @@ void cycleMemes(qk_tap_dance_state_t *state, void *user_data) {
|
|||
register_hex32(pgm_read_dword(&unicode_map[state->count+15]));
|
||||
unicode_input_finish();
|
||||
}
|
||||
else if(state->count <= 5) {
|
||||
else if(state->count <= EMOJIBLOCK) {
|
||||
tap(KC_BSPC);
|
||||
unicode_input_start();
|
||||
register_hex32(pgm_read_dword(&unicode_map[state->count+15]));
|
||||
|
|
|
@ -1,6 +1,9 @@
|
|||
# Tap Dancing to different beats.
|
||||
Tap Dance is constrained normally by `TAPPING_TERM` defined in your keyboard's config.h This proves to be challenging to work with when sometimes you just need more time to tap out your dance.
|
||||
Tap Dance is constrained normally by `TAPPING_TERM` defined in your keyboard's config.h This proves to be challenging to work with when sometimes you just need more time to tap out your dance, or even a different "beat".
|
||||
|
||||
|
||||
|
||||
- `ACTION_TAP_DANCE_FN_ADVANCED_TIME(user_fn_on_each_tap, user_fn_on_dance_finished, user_fn_on_dance_reset, tap_specific_tapping_term)` : This works the same as `ACTION_TAP_DANCE_FN_ADVANCED` just with the extra `tap_specific_tapping_term` arguement at the end. This way you can set a specific tap dance to have a longer or shorter tap in between your taps, giving you more, or less, time in between each tap.
|
||||
|
||||
- `ACTION_TAP_DANCE_FN_ADVANCED_TIME(user_fn_on_each_tap, user_fn_on_dance_finished, user_fn_on_dance_reset, tap_specific_tapping_term)` : This works the same as `ACTION_TAP_DANCE_FN_ADVANCED` just with the extra `tap_specific_tapping_term` arguement at the end.
|
||||
|
||||
`tap_specific_tapping_term` should be the same type and range of values that one would put into the `TAPPING_TERM` definition in the config.h file.
|
||||
|
|
Loading…
Reference in New Issue