cbabc8dbe6
* Replace Tapping Force Hold feature with Quick Tap Term * Replace keyboard level TAPPING_FORCE_HOLD with QUICK_TAP_TERM 0 * Deprecate force hold in info_config.json * Before and after quick tap term unit tests * Quick tap unit tests iteration * Keymap config.h correction * Remove TAPPING_FORCE_HOLD_PER_KEY macros that were missed * Add two more test cases for quick tap * Replace TAPPING_FORCE_HOLD with QUICK_TAP_TERM in configs #2 * Replace TAPPING_FORCE_HOLD_PER_KEY with QUICK_TAP_TERM_PER_KEY in configs #2 * Add function declaration for get_quick_tap_term Co-authored-by: Stefan Kerkmann <karlk90@pm.me> |
||
---|---|---|
.. | ||
keymaps/default | ||
10_helix_r.c | ||
10_helix_r.h | ||
config.h | ||
info.json | ||
readme.md | ||
rules.mk |
readme.md
navpad 1.0 with Helix (Right hand side)
Navpad connected with helix keyboard (Right Side)
- Keyboard Maintainer: yushakobo
- Hardware Supported: Navpad 1.0 PCB and Helix PCB, Pro Micro
- Hardware Availability: https://shop.yushakobo.jp/products/navpad-10
Make example for this keyboard (after setting up your build environment):
make yushakobo/navpad/10_helix_r:default
Flashing examples for this keyboard...
Helix side:
make yushakobo/navpad/10_helix_r:default:avrdude-split-right
Navpad side:
make yushakobo/navpad/10_helix_r:default:avrdude-split-left
See the build environment setup and the make instructions for more information. Brand new to QMK? Start with our Complete Newbs Guide.
Bootloader
Enter the bootloader in 3 ways:
- Bootmagic reset: Hold down the key at (0,0) in the matrix (usually the top left key or Escape) and plug in the keyboard
- Physical reset button: Briefly press the button on the back of the PCB - some may have pads you must short instead
- Keycode in layout: Press the key mapped to
QK_BOOT
if it is available