keyboard-configurator VS qmk_firmware

Many or most of their keyboards are configurable these days. See https://github.com/pop-os/keyboard-configurator

Reported at https://github.com/pop-os/keyboard-configurator/issues/195 - I get a failure from dfu-programmer trying to update using the alternate update method with the keyboard-configurator app (because fwupdmgr won't update it because of the firmware bug that the new firmware addresses).

I found the ticket regarding Fn lock https://github.com/pop-os/keyboard-configurator/issues/159

keyboard-configurator

Good. I bought Darter Pro recently and had to - business as usual under Linux - compile this and tweak that. Via things like their keyboard configurator[1] I was exposed me to Rust's GTK bindings. It wasn't pretty: the mismatch between the obviously object-oriented GTK and Rust which doesn't do (and doesn't want to) OOP was glaring. I understand the appeal of Rust very well, and I'm happy they write their drivers and (parts of) firmware in it, but it's about as fit for OOP-based GUI as Go and Erlang. Which is to say - not very much.

[1] https://github.com/pop-os/keyboard-configurator

That's exactly what it's meant for, but the frontend of the configurator app doesn't seem to list those characters. You may consider opening an issue and relating to this one: https://github.com/pop-os/keyboard-configurator/issues/105

Probably a good issue to open here: https://github.com/pop-os/keyboard-configurator

Write a keyboard firmware + configuration app in Rust for it: https://github.com/system76/qmk_firmware

What's different with the Launch 2? Is that refresh the new focus (as far as keyboard development) until it comes out?

I have a Launch keyboard and love it. I got curious the other day as to when a new firmware is going to be released and came across a pull request for a "Launch Lite" at https://github.com/system76/qmk_firmware/pull/21

It does use QMK as a base for the firmware which is nice: https://github.com/system76/qmk_firmware

But you can try this, however. You need to clone this repo: git clone https://github.com/system76/qmk_firmware.git

Use our fork. https://github.com/system76/qmk_firmware

Unfortunately, system76 developers added exactly that functionality to their firmware: https://github.com/system76/qmk_firmware/commit/a1ab70c3a28a...

So it is possible to reboot into the firmware update mode just by sending some bytes to the raw HID interface. Apparently they did not think about the security aspect of this feature.