Author | SHA1 | Message | Date |
---|---|---|---|
Joel Challis |
8e5cd981e1
|
Migrate features from rules.mk to DD (#23247) | 2 months ago |
Ryan |
023d644bb6
|
Move RGBLight animations to data driven (#21635)
* 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 |
9 months ago |
Ryan |
2f9f555add
|
Move `TAP_CODE_DELAY` to data driven (#21363) | 11 months ago |
Ryan |
4ae9bfd17a
|
Move `RGBLIGHT_HUE/SAT/VAL_STEP` to data driven (#21292)
Co-authored-by: Nick Brassel <nick@tzarc.org> |
11 months ago |
Ryan |
b1783db4ea
|
Move `RGBLED_NUM` to data driven (#21278) | 11 months ago |
Ryan |
2367d8129c
|
Move `RGBLIGHT_SLEEP` to data driven (#21072) | 11 months ago |
Ryan |
47966dc2a6
|
Migrate `rgblight.pin` and `RGB_DI_PIN` to `ws2812.pin` (#20303) | 1 year ago |
Ryan |
364c06d939
|
Move small macropad-ish layouts to data driven (#20341) | 1 year ago |
Ryan |
9e64300e67
|
Move matrix config to info.json, part 4 (#20001) | 1 year ago |
Ryan |
7e0299117b
|
Move encoder config to data driven (#19923)
Co-authored-by: Nick Brassel <nick@tzarc.org> |
1 year ago |
Ryan |
f9aeea64c1
|
Migrate `MCU` and `BOOTLOADER` to data-driven (#19529) | 1 year ago |
Ryan |
306e50b84c
|
Move keyboard USB IDs and strings to data driven: D (#17814) | 1 year ago |
Ryan |
4791cfae1a
|
Remove width, height and key_count from info.json (#14274) | 2 years ago |
James Young |
03791ed92a
|
Draytronics Daisy Configurator Refactor (#13325)
* correct layout data * use LAYOUT as layout macro name The defined LAYOUT_daisy is functional, but Configurator expects LAYOUT through the info.json file. As the board only supports one layout according to the open-source PCB files, use LAYOUT as the defined macro per QMK guidelines. * add layout macro alias |
2 years ago |
Blake |
c4d05010cb
|
Add Daisy, a macropad with dual rotary encoders + update Scarlet readme.md (#12221)
* Daisy first commit buggy * buggy still underglow crash * Daisy V1 * ReadMe Updates |
3 years ago |