Vial User Suggestions
OLED display support
QMK supports small OLED displays, it would be nice to have this implemented in Vial (even just being able to enter text strings for display, or to display current layer)
Under consideration
Per led rgb settings, layer rgb and other indicator rgb
Per key RGB is one of the few things that is lacking in the UI in VIA and VIAL. This seems to be often requested in places like r/olkb where per key RGB seems to be ...
Under consideration
Automatic keyboard layout backup
Vial should periodically save a backup of keyboard layout, so that it can be restored if the firmware is updated or if the layout gets reset.
Under consideration
Dynamic Key Overrides
Now that https://github.com/qmk/qmk_firmware/pull/11422 is merged to QMK, Vial should implement an interface for configuring these in GUI, similar to Tap Dance and ...
Done
A place where the community can upload VIAL-enabled firmwares
It is not an insignificant amount of work to port a keyboard to Vial and some skills are required. Would be great to have a site for sharing these. All used options ...
Under consideration
Ability to remap keys via keyboard input
When programming the keys in vial, inputting them with a connected keyboard would be nice. Searching them on the weirdly organised list below takes a while. (better ...
Under consideration
Add a resolution option to encoder
I wonder if it's possible to show a setting of encoder's resolution in vial. I think most of the time, users may have different preference of resolution for the ...
Under consideration
Option to change the look / order of the remap keys
Hello!
I'm slowly changing from VIA to VIAL and since you people actually care about the community I had an idea.
When I change the layout of my keyboard I have ...
Done
Add debounce settings
I guess that modyfing debounce from vial would be an awesome feature. I wouldn't need to reflash the keyboard to test different debounce values each time
Under consideration
leader keys
https://docs.qmk.fm/#/feature_leader_key
Leader keys should be added with all it's additional configs . Strict Key Processing , Infinite Leader key timeout, Per ...
Under consideration
Triple tap
Vial could support triple tap, the same way it support double tap.
For implementation, there is an example in QMK Tap Dance documentation: ...
Under consideration
Unicode Map Accessible in Keymap GUI
If a keyboard uses UNICODEMAP_ENABLE, there could be a tab (named "Unicode") giving easy access to these keys and properly displaying their unicode output. Other keys ...
Under consideration
Support of Italian key previews
As per title, VIAL currently doesn't support key previews for Italian layout.
It would be really great if it could, since the EurKey layout puts Italian accented ...
Under consideration
Ability to start a layout without owning a compatible device?
On startup Vial insists on detecting a device - I can't simply choose the device I want to create a layout for.
I downloaded Vial in hope to check it out, poke ...
Not planned
Add CAPS_WORD keycode to GUI
Add CAPS_WORD (CAPSWRD) to the GUI, QMK hex code 0x5DAC
https://github.com/qmk/qmk_firmware/blob/master/docs/feature_caps_word.md
Under consideration
Allow vial config to be done at a keyboard level
Currently to support vial with a keyboard the following needs to be done
- Add VIAL_KEYBOARD_UID to the config.h in the keymap folder
- Add vial.json to the keymap ...
Under consideration
Persistent sideload files folder
I would be so awesome to have a dedicated folder that one can drop "that other tool" `.json` files into. And then when Vial starts up (or detects a KB) it can do it's ...
Under consideration
some way to generate a nice vizualizer of your keymap
a feature that would basically take a a screenshot of every layer / selected layers and stitch the image together (either overlay the layers or put them below each ...
Under consideration
Add support to color individual key icons in vial layout UI
Problem:
Ergo keyboards with custom levels of stagger can get a little hard to keep track of the home row, especially if you're looking at a new-to-you model, ...
Under consideration
App switch keystroke function for alt-tab command-tab
Add a custom keystroke function, FN_ALTTAB (like how Via has FN_MO13 and FN_MO23) for alt-tab (or for Mac, command-tab FN_CMDTAB).
Ideally, tapping this key would ...
Under consideration
Repeat macros support
I think a convenient function to support repeat macros is a good idea
Under consideration
Include additional RGB configs in the GUI
if possible most of these addtioanl config.h options would be useful for RGB, I often find myself reflashing the firmware to finetune the RGB_DISABLE_TIMEOUT but the ...
Under consideration
Save last folder used in "Save current layout"
Under consideration
Text macro fix for different keymaps
Right now, text macros are wrong when using different language layouts because it assumes default layout. It tries to replace special characters with unicode, but ...
Under consideration
Add Tri_layer_state
I feel like since this is an integral part of a lot of peoples keymaps it should be something that can be toggled in the QMK settings page.
I would like to mention ...
Under consideration
jump to next element after input
An example of this would be combos. After choosing the "key 1" item, it should jump to "key 2" as the active element. This would make it a smoother workflow than ...
Under consideration
Add ability to create layer aliases in the json defs.
Some keyboards use layers to define certain feature sets, specifically kb's with dip switch functionality.
It would be nice to be able to add UI aliases to the ...
Under consideration
Add layer mod to layer tab in the UI
Currently there is no ui item for LM(layer,mod) in the GUI. As a workaround it can be added with the ANY macro, but should be included as well in the GUI.
Under consideration
Print/Export Cheat-Sheet
Add possibility to export current Layout as PNG respecting local Layouts (such as German "{" ones) and Combos (Eg: JK=backspace should be visible in the Export)
Under consideration
Remove keymapping or qmk settings from VIAL GUI if it's not included in the firmware.
If possible, do not include features that are not added into the firmware's build.
For example, if One shot modifiers, cadet or certain RGB modes are not included ...
Under consideration
A (printable) list view for combos, key overrides, macros etc.
A list view could be more informative than switching between 32 tabs.
e.g. Combos:
01 [key] + [key] = [key]
02 [key] + [key] + [key] = [key]
03 [key] + [key] = ...
Under consideration
add script to pull json from the-via repo on github
the via jsons will work for building vial and this should be made known to those reading the documentation. There is no reason for people to need to make their own ...
Done
Add Midi CC (control change)
Midi CC for midi2lr read value, important for lightroom usage as midi2lr wont read midi notes from vial or qmk. I already did qmk sent midi cc and midi2lr can read it.
Under consideration
option to fully disable vial's dynamic combos, tap dance and key overrides
i would like to use the standard qmk equivalent of these features and define them in code, in keymap.c, rather than vial.
however, currently there is no such way of ...
Under consideration
Unify UI in regards to saving.
Some UI tabs don't require a save after editing (Key overrides,combos ) , while some do (tap dance, macros etc). Would be nice if the UI was consistent between both, ...
Under consideration
Allow Dynamic Number of Macros
Allow dynamic adding and removing of macros in ViaL, this would allow users with very macro heavy workflows to configure all of those in gui.
Adding macros could ...
Under consideration
An equivalent to "caniusevia.com"
It would be helpful to link users to the VIAL version of https://www.caniusevia.com/docs/supported_keyboards
Under consideration
Add ability to predefine tap dance in config.h or similar
Right now, you're not able to use QMK tap-dance with Vial dynamic tap-dance. You can disable Vial tap-dance functions in vial.c/vial.h and use the QMK tap-dance but ...
Under consideration
KC_LOCK implementation
KC_LOCK works when defined in json but can only be defined in Vial by double clicking the key and assigning '0x5d2a'. Otherwise, it works as intended.
Under consideration
show nicer shifted keys
currenty, shifted key is shown as the original key wrapped in lsft. this is fine for telling it's automatically appling shift, but can be slighly confusing when ...
Under consideration
Autoshift toggle & Combo toggle keys in Quantum Keys
This would be a quality of life change: add an AutoShift toggle (KC_ASTG - currently 0x5C1A on my keyboard) and a Combo toggle (? -- currently 0x5CF9 on my keyboard) ...
Done
Add ability to copy or reorder layers in the GUI
It could be very convenient for experiments with a lot of layers:
- copy definitions of current layer to a new one
- reorder layers
Even more convenient would be ...
Under consideration
Organize keys better to make them easier to find
They keys in the Quantum-tab are somewhat sorted, but very hard to find. A simple Headline for each section (mod, hold tab mods, etc) would be really helpful already. ...
Under consideration
Add retroshift to qmk settings
https://docs.qmk.fm/#/feature_auto_shift?id=retro-shift
Retro-shift is a key component to people that use tap-hold home row mods, and also uses autoshift, without ...
Under consideration