Took me a bit to figure why my keyboard has a dedicated "open readwise" button but now it's pretty straightforward. There's a bit of a weird code that takes the keycode (this is the keyboard-internal code) and maps it to pressing (or releasing) a number of other keys. You can see how KC_SNAP maps to shift-cmd-4 in key_comb_list. What's shift-cmd-4? It's "open the fourth app on the taskbar".
Now, what happens if you accidentally press two of those magic keys at the same time and mix up the release order? Well, fun shit happens!
My weekend is now reclassified as "make the keyboard do what I want it to do." How many cycles can STM32F401's flash withstand? Because this is going to be a long day and they don't even have an EEPROM, they just do wear leveling over the flash.
[#]keychron
=> View attached media | View attached media | View attached media | View attached media
=> More informations about this toot | More toots from farcaller@hdev.im
ST docs seem to say it's about 10K erase cycles. Whelp. That's not a lot given any button press on the web UI results in the flash write.
Well then, VIA will go away first, who needs the web UI anyway.
=> More informations about this toot | More toots from farcaller@hdev.im This content has been proxied by September (ba2dc).Proxy Information
text/gemini