Dactyl-It-Yourself-Editor VS vial-gui

But I've been building keebs for a few years now, and I gotta cut back :-P The biggest issue is it takes forever to print a shell to 'test fit' it. It would actually be cool if you could print the shells upside down so you don't have to print the whole thing to see how it feels.

Oh! looks like there's a OpenSCAD parametric dactyl now (1) I think this was the clojure one I was playing with before: (2)

1: https://github.com/pseudoku/Dactyl-It-Yourself-Editor

2: https://github.com/l4u/dactyl-manuform-mini-keyboard

Link to Miniwarp https://github.com/pseudoku/Dactyl-It-Yourself-Editor/blob/master/Things/MiniWarp.stl

I used Dactyl-It-Yourself-Editor to create the base model. Further heavily modified in Fusion360.

The original Hypo Warp is all MX based and it is available on github. So you can use that one instead.

Thanks, the board is a MiniWarp by Pseudoku. The stl is in their github repo

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