xs5871

@ldsands: from the QMK docs I couldn't figure out how the chaining "is supposed to" work (or even find a mention of it), and I don't feel like digging through...

Hint to the person implementing this documentation: we also provide a compile target for mpy_cross: ```bash $ du -sh kmk 488K kmk $ make compile $ du -sh .compiled/kmk 228K...

I thought about the speed limit and acceleration in general. Most mouse HIDs don't do acceleration on the hardware / client device, but on the host driver side. The reason...

The movement resolution is a problem. It looks like the trackball resolves around 5-10 degrees on the major axes. Diagonal movement is very jittery, even without scaling. It helped a...

Now it fails in the runner again. Can not reproduce with python3.10. Can reproduce with python3.8.

I put the sleep statement in to emulate KMKs maximum loop execution frequency. I get the tests to pass if I paste a bunch of `self.keyboard._main_loop()` at the end of...

I don't believe that a callback is the best way to go about this. Would could argue about the shortcomings: it's opaque; can't be validated; you don't no where, when...

Proper RPC / two-way communication isn't going to happen (from my side) until the split code has been de-spaghettified.

This may be an ignorant question: isn't that the same as the tapdance `KC.TD(KC.MT(KC.X, KC.LSFT), KC.X)` for example?

I still think this would be better suited as a special case of tapdancing. We can improve tapdance to resolve the last key in a sequence immediately, that's a good...