023d644bb6
* Move RGBLight animations to data driven, 0-9 * Move RGBLight animations to data driven, A * Move RGBLight animations to data driven, B * Move RGBLight animations to data driven, C * Move RGBLight animations to data driven, D * Move RGBLight animations to data driven, E * Move RGBLight animations to data driven, F * Move RGBLight animations to data driven, G * Move RGBLight animations to data driven, H * Move RGBLight animations to data driven, handwired * Move RGBLight animations to data driven, I * Move RGBLight animations to data driven, J * Move RGBLight animations to data driven, K * Move RGBLight animations to data driven, L * Move RGBLight animations to data driven, M * Move RGBLight animations to data driven, N * Move RGBLight animations to data driven, O * Move RGBLight animations to data driven, P * Move RGBLight animations to data driven, Q * Move RGBLight animations to data driven, R * Move RGBLight animations to data driven, S * Move RGBLight animations to data driven, T * Move RGBLight animations to data driven, U * Move RGBLight animations to data driven, V * Move RGBLight animations to data driven, W * Move RGBLight animations to data driven, X * Move RGBLight animations to data driven, Y * Move RGBLight animations to data driven, Z * Fix incorrect placement * Fix build failures and mismatches |
||
---|---|---|
.. | ||
4x5 | ||
4x5_5 | ||
4x6 | ||
4x6_5 | ||
5x6 | ||
5x6_2_5 | ||
5x6_5 | ||
5x6_6 | ||
5x6_68 | ||
5x7 | ||
6x6 | ||
6x6_4 | ||
6x7 | ||
dmote | ||
config.h | ||
readme.md |
Dactyl ManuForm
Forked from the Dactyl, the Dactyl ManuForm is a parameterized, handwired, split bodied, tented, concave key-well design that incorporates the thumb cluster from the ManuForm.
- Keyboard Maintainer: Tom Short
- Hardware Supported: Pro Micro, or clone of
- Hardware Availability: Github
Variants
Dactyl ManuForm's are built in variations that cater for different row and column counts, and thumb clusters.
As standard:
- The finger keywell bottom row has 2 keys, 1 each in ring and middle columns
- Exception to this rule is the
5x7
variant - that has two additional keys, per half, in this row
- Exception to this rule is the
- The thumb cluster has 6 keys, arranged in a staggered 2 columns by 3 rows
Variants are denoted as RowCount
xColumnCount
(_Alteration
)
Row
Count | Description |
---|---|
4 | Three rows, typically for alphabet and some puncuation characters, with 2 key (finger keywell) bottom row |
5 | As 4 row with number row above |
6 | As 5 row with function row above |
Column
Count | Description |
---|---|
5 | A column for each finger with additional column for first finger |
6 | As 5 column with additional pinky finger column |
7 | As 6 column with either an additional first finger column (5x7 ) or additional pinky column (6x7 ) |
Alteration
Code | Description |
---|---|
5 | Thumb cluster replaced with five key thumb cluster of Dactyl Manuform Mini |
2_5 | Same as code 5 with two additional keys added to finger key-well bottom row |
Case Files Generator
Dactyl Generator, created by rianadon, is a web based file generator that negates having to compose case files using programming languages, which was the matter when using the original Dactyl and Dactyl ManuForm GitHub repos, by instead compiling case files based on options and parameters configured in a web front end.
Compile
Make example for this keyboard (after setting up your build environment) in the 5x6 variant:
make handwired/dactyl_manuform/5x6:default
Flashing example for this keyboard:
make handwired/dactyl_manuform/5x6:default:flash
See the build environment setup and the make instructions for more information. Brand new to QMK? Start with our Complete Newbs Guide.
Keymaps
Default
The default functional layout, based on QWERTY, and every variant has this keymap; used as a starting point/template for custom keymaps and for debugging purposes when soldering key matrix to controller.
VIA
Similar to Default but adds support for the VIA keymap configurator. Layer count set to 4 to comply with VIA defaults, and remaps keys to accommodate this constraint, if applicable.
Variants with VIA support:
- 4x6
- 5x6_5
- 5x7
Miryoku
For more information on this layout schematic, please see the Miryoku Reference Manual.
For QMK specifics, please see Miryoku QMK.
Variants with Miryoku support:
- 4x5
- 4x5_5
- 4x6
- 4x6_5
- 5x6
Non-Pro Micro Controller Compilation
If building a Dactyl Manuform with controllers that aren't a pro micro, the Converter feature of QMK will allow compilation of firmware for the intended variant and supported controller without having to create a new QMK keyboard/keymap.
Please see Converters documentation for list of controllers that are supported converting from pro_micro
and how to implement conversion.
Flashing
To flash your board with generated firmware file, please see Flashing Instructions and Bootloader Information
Handedness configurations
See Handedness documentation for more information on configuring handedness/master half.
VIA Configuration
Variants with a via
keymap are VIA capable.
Compile firmware, for enabled variant, with it's via
keymap and flash board with this firmware file.
qmk compile -kb handwired/dactyl_manuform/4x6 -km via
Bootloader
Enter the bootloader in 3 ways:
- Bootmagic reset: If enabled, 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 or controller - some may have pads you must short instead
- Keycode in layout: Press the key mapped to
QK_BOOT
if it is available