vial-gui VS vial-qmk

> 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 wish to enable several features on my corne thru vial but could not seem to make those from this link to compile - first error was about keycode then something about dynamic keymap when i had the first fixed/simplified. i'd appreciate if anyone could share their tested vial configuration files that i can use as guide.

This applies to OP as well, if you have any Keyboard @ https://github.com/vial-kb/vial-qmk/tree/vial/keyboards/keychron

You'll probably need to download the files from the GitHub repository for Vial or QMK. Depending on what you prefer and what you need. Then you'll have to learn what you need to change to set up the screens and then to edit the files. Your keyboard maker probably can provide you some files you can use. Then you'll have to compile your own HEX file. And only after that you can re-flash your keyboard and use all those amazing things you integrated into the firmware.

It looks like that's a vial keymap specifically for the rev2? I don't know whether it would make a difference, but you could try to compile from this keymap instead and see if it works?

According to this (https://github.com/vial-kb/vial-qmk/blob/vial/keyboards/bastardkb/charybdis/4x6/v2/splinky/config.h) the Vial firmware for Splinky based Charybdis is written natively using RP2040 pin names.

Think you can also port to VIAL? I am currently using the doio firmware without problems, but guessing your updates will be useful: https://github.com/vial-kb/vial-qmk/tree/vial/keyboards/doio/kb16

I've been using VIA to edit my keyboard layout, but unfortunately the software can't find my keyboard anymore (it just gets stuck on 'Searching for devices'). I think I need to reflash my keyboard. I don't have any .hex files for it with QMK toolbox, and the libra mini doesn't show up in the list of keyboards on the online QMK configurator. I do, however, have access to the files found in vial-qmk/keyboards/libra_mini/keymaps/vial (found here https://github.com/vial-kb/vial-qmk/tree/vial/keyboards/libra_mini). I've been using the vial.json file from there to change the layout up until now. How would I go about getting a .hex file, or better yet, a keymap.JSON file compatible with the online QMK configurator?