Pinky4 VS vial-gui

found it: https://github.com/tamanishi/Pinky4 looks like my next build 😄

I've already used a multimeter to verify that the TRRS cable is connecting the correct pins across both boards on the TRRS connector, and even verified that they're connecting the correct pins on each pro micro controller (e.g. GND to GND, VCC to VCC, Data to Data) according to the PCB layout (https://github.com/tamanishi/Pinky4/tree/master/pcb)

In my experience it does become harder to type on staggered keyboards unless you're continuing to do it regularly. You may need to relearn to do that. Same deal with continuing QWERTY usage.

VIA is proprietary and not really an official QMK thing (QMK is free software). There is also Vial[0] which is free software if you want a GUI, and the QMK configurator[1] web app (but this lacks some features like enabling mouse keys or NKRO).

Lastly I want to add that Workman[2] may be preferable to Colemak Mod-DH. Rather than an attempt to fix major issues in Colemak like Mod-DH, it's a whole new layout that avoided the issues from the start. I have also heard from some that it had ortholinear and columnar stagger boards in mind with its design.

I type on a Pinky4[3] keyboard that I assembled from a kit. More keys than your keyboard, but a similar idea. I was coming from a 60% and wanted a similar amount of keys. I've been quite happy with it.

[0] https://get.vial.today/

[1] https://config.qmk.fm/#/

[2] https://workmanlayout.org/

[3] https://github.com/tamanishi/Pinky4

and this one may not fit your requirements since it doesn't have the full bottom row, but a personal favorite, pinky4

I'm currently evaluating which keyboard to build. There are currently 2 main contenders: zodiark and pinky4 The sofle I also took into consideration but I would like to have a few more keys than 58. There are some pros and cons for both boards

you might want to take a look at PCB designs such as the Pinky4: https://github.com/tamanishi/Pinky4 (or Pinky3)

> 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/