qmk_firmware VS qmk_firmware

I agree that reduced finger movement is a crucial step in achieving typing efficiency. This is nicely solved by mod tap modifiers in QMK/ZMK[1] where key acts as a char when tapped and as a layer while pressed.

[1]: https://github.com/qmk/qmk_firmware/blob/master/docs/mod_tap...

Separate wireless controller, see the glue code at [0]

[0]: https://github.com/qmk/qmk_firmware/compare/master...nuphy-s...

If you have a keyboard that runs QMK firmware[0] with the VIA[1] feature enabled[2], then there is a convenient testing app available from the same place you customize your keys [3].

[0] https://qmk.fm/

I made a layout that I'm happy with. Spanish is my native language, so it has characters like the accents and 'ñ', but it's meant to be used for programming as well. Visual Studio uses a lot of Ctrl and Ctrl + Shift shortcuts, so I left them in the same place as the default Corne layout so I can press them both with my pinkie finger. Perhaps some of the ideas are useful to you.

Also, it would be possible to do this for the RP2040. However, it needs some work to get working. but for example: https://github.com/qmk/qmk_firmware/pull/20999

Ok, it's an ST7735, not too different from the ST7789. You should be able to get running by looking at their files in the QMK repo and going from there. You should also check their resources page.

UPDATE: after fluffing around a little bit, I have manged to fix this code: https://github.com/qmk/qmk_firmware/blob/master/keyboards/lily58/keymaps/bongocat_wpm_responsive/keymap.c and flash it successfully - it seems not to be working correctly as the cat is only hanging there and does not respond to the wmp count. If anybody spots anything wrong in the code please let me know!(C is not my language but I am a programmer, I am gonna get at it again over the weekend if I have time left)

Oh, it was actually this guy https://github.com/treeman/qmk_firmware/blob/master/keyboards/ferris/keymaps/treeman/repeat.c . I wonder how your implementations differ.

I sure do.

I've made some blog posts about it: https://www.jonashietala.se/blog/tags/t-34/, although they're a bit outdated right now. The source code is more up to date: https://github.com/treeman/qmk_firmware/tree/master/keyboards/ferris/keymaps/treeman

I haven't made a write-up of what I'm currently running, but it's on Github.

I have my own implementation. See repeat.h and repeat.c and how it's used in keymap.c. You can ignore the "reverse repeat", making the implementation quite simple.

Here's a blog post of my layout and here's the current layout in code (which has some smaller changes to the base layer).

This is my current 34-key layout. Some notable features:

This is my qmk keymap and here's a blog post about the keymap (although I've made some changes since then).

I fear, if you want a highly customized layout on a highly customized board, you have to work a little for it ˄˄ But the author put his code on github, so you can start from there: https://github.com/treeman/qmk_firmware/tree/master/keyboards/kyria/keymaps/treeman My tip: use his Kyria version, and just consider which keys will be obsolete, and you can not use. Then try to flash on the Gergoplex.

I can't really call it "my" CAPSWORD, since I got the idea from /u/jonas_h and it looks like several others have contributed to it. That said, it looks pretty easy to extend to handle additional characters by adding extra cases to this switch statement. If you have a continuous range you want to add, you can use the KC_A ... KC_Z syntax. Otherwise, you'd have to add them one per line, but it's still pretty doable.