vial-gui VS QwickSteps

> made the customization much more comfy, without the need of recompile the fw

Get someone to write a profile for https://get.vial.today/ support.

> add a damn service to print easily custom keycaps

https://www.wasdkeyboards.com/custom-text-cherry-mx-keycaps....

> please STOP making cherry, OSA etc profiles

They are making them because people keep buying them. Turns out most people actually like typing on them.

Less drastic than reflashing could be to reset to factory defaults. Note that this will wipe out any Via/Vial configuration and other configuration (e.g., RGB mode, RGB colour settings, and NKRO setting).

At all possible? Yes, but probably not from Via. I don't know about Vial (it requires special versions of the keyboard firmware).

This is the second one I’ve built but it’s for someone else, this is too many keys for me lol. The case is printed in a super nice matte green then it uses Boba U4Ts that sound and feel super nice. The keycaps are just a placeholder while I test the board, I’m certain they’ll put something that matches. The board is fully compatible with Vial and runs on a USB-C Pro Micro.

VIA doesn't have any support for configuring tap-dances, nor does the QMK Configurator. Your two options are either using VIAL https://get.vial.today/. Or utilizing the feature directly in QMK source code https://docs.qmk.fm/#/feature_tap_dance.

This firmware update will make it compatible with open source software called Vial... https://get.vial.today/

This was my exact scenario, and I ended up flashing my keyboard with Vial QMK. It’s a Via-like interface that allows you to edit additional QMK settings like the tap-hold timings.

resources I've tried: https://docs.qmk.fm/#/newbs_getting_started https://get.vial.today/

I'm using a typical ten-keyless keyboard that otherwise has a standard US 103 ANSI layout. My need for remapping keys is for the letters as I accidentally developed[0] my own custom non-Qwerty layout[1] that turned out to be very similar to NIRO.

[0] https://github.com/qwickly-org/Qwickly

[1] https://github.com/qwickly-org/QwickSteps

I'm also 50+ and had issues with shooting pains along the back of my hands. My solution was to use a keyboard layout that reduces awkward finger movements. I tried some alternative keyboard layouts but wasn't happy with how hard they were to learn and ended up making my own[0] that ends on the Qwickly layout[1] that was easier to transition to compared to Colemak/Tarmak.

My error rate is probably still higher than using Qwerty but my hands are more comfortable so worth the tradeoff. I also learned that I don't type all that much while coding, spending much more time thinking than typing and had to use a practice site[2] to get enough practice to learn a new layout.

[0] https://github.com/qwickly-org/QwickSteps

[1] https://github.com/qwickly-org/Qwickly

[2] https://www.keyhero.com/free-typing-test

I'm a software dev and thought that learning a new layout would help me. It does, but not in the way I thought it would. I found that the normal amount I type every day isn't enough to actually learn a new layout and that I had to go to sites like keyhero.com a few times per day to get enough typing volume. The greatest benefit I've learned is that my hands are so much more comfortable and I never get pains along the backs of my hands that I used to get. I too struggled with Colemak (and the Tarmaks) then gave it up to learn a layout I made that I thought was easier to learn and as fast or faster. I use the Qwickly-KZ (pinky comma) variant and there's QwickStep layouts along the lines of Tarmak.