qmk_firmware VS vial-qmk

I had trouble with HMR as well at the beginning, but since switching to sunaku's fork/PR I've almost eliminated all the issues I had with it. And worth mentioning is urob's timeless HMR config from which I think the fork/PR takes some of its inspiration.

Affirmative. I updated my fork and my clone last week. I also did a second, fresh clone and merged this PR: https://github.com/manna-harbour/qmk_firmware/pull/56

Im guessing installing something like this is what i need to do? https://github.com/manna-harbour/qmk_firmware/pull/56

See my Miryoki PR for details: https://github.com/manna-harbour/qmk_firmware/pull/56

I have a separate system for that as part of this old unreleased project. They're orthogonal so could be used together, but it'd be nicer if they were integrated. If you just want to remap buttons or map buttons to keys you can do that in the OS.

Well, things like Bilateral Combinations are aware of which hand is using the modifier to only apply it to the other side's presses & minimise accidental triggering on same-hand rolls.

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?