vial-gui VS qmk_distro_msys

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

- QMK MSYS: you'll need it for many things, for compiling your firmware file and for flashing, especially if flashing with QMK Toolbox isn't permitted in firmware settings (in this case QMK Toolbox just won't recognize your keyboard);

You don't need the GUI though, you can write the simple code yourself, then using QMKMSYS you can compile these flat text files into firmware. Using the appropriate flashing software for ypur microcontroller, you then flash this firmware onto your keyboard.

First, install QMK MSYS from here. Once installation is finished, DO NOT DO "QMK SETUP". I will explain this later.

Download QMKMSYS.exe from https://github.com/qmk/qmk_distro_msys/releases/tag/1.7.2

QMK MSYS: What we will be using to compile the firmware

You don't really need to be able to program though. (Assuming you use Windows) QMK MSYS will help put all the QMK code on your PC and make it ready to make the firmware file, you will just specify which keyboard make & model you have, edit the file line that controls the timing behaviour, and your PC will build the firmware. Then the Toolkit GUI app will help you sync that onto the keyboard.

Download and install latest version of QMK MSYS

a) Installed git for windows. (If you don't know how to use it - don't go this way. Just download qmk-vial as ZIP, extract in "C:\Users\URUsername\qmk_firmware\vial-qmk", install QMK MSYS. Run it from shortcut in installed folder, run "qmk setup -H C:\Users\URUsername\qmk_firmware\vial-qmk" and change directory "cd C:\Users\URUsername\qmk_firmware\vial-qmk" for next steps.) b) Had an error with gh, so installed cli. Cloned qmk-vial with github desktop in the end. c) Had an error with "make", so installed it and cloned submodules. d) Still had an error with "make" when compiling fw "No rule to make target".