xs5871
xs5871
This is an approach to make modules with side effects more consistent (related to #495). At the moment, I think only hold-tap (and it's decendents) and combos profit. Modified keys...
Every application needs a gaping hole in security, ready to be exploited. I don't even remember how I got the idea, but in the past people were asking questions like...
There's currently no intuitive way to access modules and extensions, other than passing (effectively) global variables around. Suggestion: Let `keyboard.modules` (, extensions respectively) be a container class similar to the...
I liked the intent of #461: Reduce some of the repetitiveness of the module and extension interface invocations. The least invasive (or contentious) solution would be a wrapper for the...
There's no consistent or central debugging mechanism. The current debug prints from `KMKKeyboard` can be _very_ verbose to the point of being counterproductive in some scenarios. In my testing branch...
RGB animation mode knight raises an out-of-bounds error.
The split module has a lot of "if BLE:" and "if UART:" patterns in it, which will get worse with the addition of a PIO UART and someday a one-wire...
As discussed in #562 here's a draft of how to seperate the BLE communication logic out into a "black box" transport. The idea is to have "transports" that handle the...
**Is your feature request related to a problem? Please describe.** We have a spell checking script now, but no integration. **Describe the solution you'd like** Add a github action for...
I think there was a reason we didn't do this from the start. Can't remember it and all the unit tests pass, so... Leaving this as a draft for now?