Closed tinyboatproductions closed 2 months ago
Confirmed: I got the same error running todays version of KMK on CircuitPython 8.2.7 (because thats what my production keyboard is currently running)
I reverted back to a KMK version from around the same date as the CircuitPython version (2023-10-19) and the code copiles without error.
wow @xs5871, how long did it take you to write up pull request 1026?
Testing with updated rapidfire.py from pull 1026 works. Also that was fast af.
wow @xs5871, how long did it take you to write up pull request 1026?
Fixing the reported issue: maybe 20 seconds. A tiny and obvious mistake that only happend because there were zero unit tests. Adding unit tests, getting confused about weird inconsistent behavior (to the point were I was amazed how it wasn't reported as fundamentally broken long ago), fixing that + the rewrite because I got anoyed by all the jank: more like 4-5 hours.
Thanks for sharing. Good info and more for me to learn. Could you, by any chance, point out the obvious mistake?... for those of us curious enough to look thru the code and your PR for 30minutes and couldn't find it
**kwargs
needs two asterisks to pack/unpack into a dictionary, i.e. catch additional named (=keyword) arguments like on_press
which aren't explicitely defined in the RapidFireKey
constructor.
Describe the bug When trying to setup RapidFire on a new install any RapidFire key presents the "unexpected keyword argument 'on_press' " error.
To Reproduce Steps to reproduce the behavior:
Expected behavior Expect it to behave as RapidFire keys used to. Rapid key presses of the provided key code
Debug output
Additional context
main.py: