docs/ChangeLog/20200829.md
Four times a year QMK runs a process for merging Breaking Changes. A Breaking Change is any change which modifies how QMK behaves in a way that is incompatible or potentially dangerous. We limit these changes to 4 times per year so that users can have confidence that updating their QMK tree will not break their keymaps.
Keyboards released by The Key Company and keyboards designed by flehrad have moved to vendor folders. If you own any of the keyboards listed below, please use the new names to compile your firmware moving forward.
| Old Name | New Name |
|---|---|
| candybar/lefty | tkc/candybar/lefty |
| candybar/righty | tkc/candybar/righty |
| m0lly | tkc/m0lly |
| tkc1800 | tkc/tkc1800 |
| bigswitch | flehrad/bigswitch |
| handwired/downbubble | flehrad/downbubble |
| handwired/numbrero | flehrad/numbrero |
| snagpad | flehrad/snagpad |
| handwired/tradestation | flehrad/tradestation |
This pull request changes the configuration for Keebio split boards to use the same RGB strip wiring for each half, which provides the following improvements:
If you have customized the value of RGBLED_SPLIT for your keymap, you will need to undefine it using #undef RGBLED_SPLIT before defining it to your customized value.
This change affects:
Allows the Combo feature to support more than 256 combos.
Any fork that uses process_combo_event needs to update the function's first argument to uint16_t:
void process_combo_event(uint8_t combo_index, bool pressed)void process_combo_event(uint16_t combo_index, bool pressed)BOOT0.BOOT0 is low), then the built-in bootloader will skip any sort of DFU.BOOT0 high before issuing the system reset. As the RC circuit takes a while to discharge, the system reset executes the ROM bootloader which subsequently sees BOOT0 high, and starts executing the DFU routines.ACTION_TAP_DANCE_FN_ADVANCED_TIME dance.JOYSTICK_ENABLE = yes to your rules.mk and
#define JOYSTICK_BUTTON_COUNT 8
#define JOYSTICK_AXES_COUNT 2
RGBLIGHT_EFFECT_CHRISTMAS_INTERVAL has been greatly decreased; please check your animation if you have customized this value.st-flash utility from STLink Tools is now supported (#9964)dump_vars, which allows for printing out all the variables that make knows about, after all substitutions occur.make handwired/onekey/proton_c:default:dump_vars/platforms/chibios as previously discussed on discord.chconf.h, halconf.h, and mcuconf.h files within the platform definition, which is able to be overridden by the keyboard directly, though include path ordering.chconf.h, halconf.h, mcuconf.h, and board.h that can be dropped into a keyboard directory, in order to override rather than replace the entire contents of the respective files.keyboard_led_stats in lufa.c and ChibiOS usb_main.c to keyboard_led_state, as well as vusb_keyboard_leds, for consistencyENDPOINT_CONFIG macro, it seems pointless and removes the need for endpoint address defines in the middle of the endpoint numbering enumGET_REPORT request handling. Not sure about this one, but the existing code appears to always return an empty report - now send_keyboard sets this variable to the current report, matching what the LUFA code does.CONSUMER2BLUEFRUIT() and CONSUMER2RN42() macros to static inline functions (#9055)debug() calls to dprintf(), moved raw_hid_report out of the way so that we can implement the shared endpoint stuff.adafruit_ble.h from ssd1306.c (#9355)outputselect.c is no longer compiled if Bluetooth is disabled (#9356)analogRead() deprecated in favor of analogReadPin() (#9023)STM32_DMA_REQUIRED when using DMA-based WS2812 driver on STM32 (#10127)