docs/ChangeLog/20210529.md
Split boards can now use RGB Matrix without defining a custom matrix.
Added support for MK66F18 (Teensy 3.6) microcontroller.
A new qmk console command has been added for attaching to your keyboard's console. It operates similarly to QMK Toolbox by allowing you to connect to one or more keyboard consoles to display debugging messages.
We've updated the qmk config command to show only the configuration items you have actually set. You can now display (almost) all of the available configuration options, along with their default values, using qmk config -a.
LED Matrix has been improved with effects, CIE1931 curves, and a task system.
The following keyboards have had their source moved within QMK:
| Old Keyboard Name | New Keyboard Name |
|---|---|
| crkbd/rev1/common | crkbd/rev1 |
| function96 | function96/v1 |
| nckiibs/flatbread60 | delikeeb/flatbread60 |
| nckiibs/vaguettelite | delikeeb/vaguettelite |
| nckiibs/vanana/rev1 | delikeeb/vanana/rev1 |
| nckiibs/vanana/rev2 | delikeeb/vanana/rev2 |
| nckiibs/vaneela | delikeeb/vaneela |
| nckiibs/vaneelaex | delikeeb/vaneelaex |
| nckiibs/waaffle/rev3/elite_c | delikeeb/waaffle/rev3/elite_c |
| nckiibs/waaffle/rev3/pro_micro | delikeeb/waaffle/rev3/pro_micro |
The Function96 V2 has also been added as part of these changes.
The codebase for the Durgod K320 has been reworked in anticipation of additional Durgod keyboards gaining QMK support.
Additionally, the crkbd/rev1/legacy keyboard has been removed.
QMK has decided to deprecate the full Bootmagic feature and leave Bootmagic Lite as the only remaining option.
This pull request changes the behavior of BOOTMAGIC_ENABLE such that specifying BOOTMAGIC_ENABLE = yes enables Bootmagic Lite instead of full Bootmagic.
If attempts to use Bootmagic functionality result in unexpected behavior, check your rules.mk file and change the BOOTMAGIC_ENABLE setting to specify either lite or full.
This is the current planned roadmap for the behavior of BOOTMAGIC_ENABLE:
BOOTMAGIC_ENABLE = yes will enable Bootmagic Lite instead of full Bootmagic.BOOTMAGIC_ENABLE must be either yes, lite, or no – setting BOOTMAGIC_ENABLE = full will cause compilation to fail.BOOTMAGIC_ENABLE must be either yes or no – setting BOOTMAGIC_ENABLE = lite will cause compilation to fail.We've removed support for LAYOUT_kc macros, if your keymap uses one you will need to update it use a regular LAYOUT macro.
To allow for keyboards to override (or not) keymap level code the encoder_update_kb function has been changed from void to bool. You will need to update your function definition to reflect this and ensure that you return a true or false value.
Example code before change:
void encoder_update_kb(uint8_t index, bool clockwise) {
encoder_update_user(index, clockwise);
}
void encoder_update_user(uint8_t index, bool clockwise) {
if (index == 0) { /* First encoder */
if (clockwise) {
tap_code(KC_PGDN);
} else {
tap_code(KC_PGUP);
}
} else if (index == 1) { /* Second encoder */
if (clockwise) {
tap_code(KC_DOWN);
} else {
tap_code(KC_UP);
}
}
}
Example code after change:
bool encoder_update_kb(uint8_t index, bool clockwise) {
return encoder_update_user(index, clockwise);
}
bool encoder_update_user(uint8_t index, bool clockwise) {
if (index == 0) { /* First encoder */
if (clockwise) {
tap_code(KC_PGDN);
} else {
tap_code(KC_PGUP);
}
} else if (index == 1) { /* Second encoder */
if (clockwise) {
tap_code(KC_DOWN);
} else {
tap_code(KC_UP);
}
}
return true;
// If you return true, this will allow the keyboard level code to run, as well.
//Returning false will override the keyboard level code. Depending on how the keyboard level function is set up.
}
develop branch. (#12723)BOOTMAGIC_ENABLE=yes to use Bootmagic Lite (#12172)qmk console (#12828)bin/qmk in favor of the global CLI (#12109)FUNC() (#12161)develop branch. (#12495)point_t -> led_point_t (#12864)send_unicode_hex_string() (#12602)b15288fb87)qmk generate-api (#12833)