Closed riskable closed 2 years ago
Wow thanks! I should have updated the chording once it got merged into keyberon.
PR looks good and I can update a couple things after it merges. Just curious, what made you submit the PR if you don't have the hardware?
Haha I know you must've been like, "WTF‽ LOL! Who is this guy‽" Here's how it happened: I was looking for an example of using an RP2040 to emulate a keyboard in Rust and this project came up. I cloned it and tried to build it... It failed (because of the hard-coded local Keyberon path). So I had a look and quickly realized it only needed trivial changes to fix it so I made them.
Then I was like, "well, I did all this work I might as well put it to good use" and submitted a PR 👍
HO HO HO Merry Christmas! :grin:
Awesome! Thanks!
I've also got these floating out there as rp2040 examples: https://github.com/camrbuss/lily58-rp2040-keyberon https://github.com/camrbuss/crkbd-rp2040-keyberon
All dependencies have been updated to their latest versions and the path to Keyberon was fixed inside Cargo.toml so it points to the github repo (which is necessary to build it because the stable release doesn't have chording yet). In order to do that I had to make a few trivial changes to the code since it didn't quite match how the new chording feature wants you to define things and there were some minor changes to rp2040-boot2 in 0.2.0 which changed how you're supposed to use it (slightly).
I tested that these changes compile and flash to an rp2040 board (an ItsyBitsy which is basically just a smaller version of the main Pico board) but I did not test using it as an actual keyboard. It should work just fine though 👍