Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Move RGBLight animations to data driven (#21635) | Ryan | 2023-08-23 | 1 | -1/+13 |
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * 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 | ||||
* | Move `TAP_CODE_DELAY` to data driven (#21363) | Ryan | 2023-06-25 | 1 | -0/+3 |
| | |||||
* | Move `RGBLIGHT_HUE/SAT/VAL_STEP` to data driven (#21292) | Ryan | 2023-06-24 | 1 | -0/+2 |
| | | | | Co-authored-by: Nick Brassel <nick@tzarc.org> | ||||
* | Move `RGBLED_NUM` to data driven (#21278) | Ryan | 2023-06-18 | 1 | -0/+1 |
| | |||||
* | Move `RGBLIGHT_SLEEP` to data driven (#21072) | Ryan | 2023-06-16 | 1 | -0/+3 |
| | |||||
* | Migrate `rgblight.pin` and `RGB_DI_PIN` to `ws2812.pin` (#20303) | Ryan | 2023-04-06 | 1 | -0/+3 |
| | |||||
* | Move small macropad-ish layouts to data driven (#20341) | Ryan | 2023-04-05 | 1 | -10/+10 |
| | |||||
* | Move matrix config to info.json, part 4 (#20001) | Ryan | 2023-03-11 | 1 | -0/+5 |
| | |||||
* | Move encoder config to data driven (#19923) | Ryan | 2023-02-26 | 1 | -0/+6 |
| | | | | Co-authored-by: Nick Brassel <nick@tzarc.org> | ||||
* | Migrate `MCU` and `BOOTLOADER` to data-driven (#19529) | Ryan | 2023-02-08 | 1 | -0/+2 |
| | |||||
* | Move keyboard USB IDs and strings to data driven: D (#17814) | Ryan | 2022-07-29 | 1 | -1/+7 |
| | |||||
* | Remove width, height and key_count from info.json (#14274) | Ryan | 2021-09-12 | 1 | -2/+0 |
| | |||||
* | Draytronics Daisy Configurator Refactor (#13325) | James Young | 2021-06-25 | 1 | -1/+4 |
| | | | | | | | | | * 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 | ||||
* | Add Daisy, a macropad with dual rotary encoders + update Scarlet readme.md ↵ | Blake | 2021-03-25 | 1 | -0/+25 |
(#12221) * Daisy first commit buggy * buggy still underglow crash * Daisy V1 * ReadMe Updates |