<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <title>Ideas for Vial</title>
  <subtitle>Ideas for Vial as submitted to our Feature Upvote board. Ideas are ordered by 'new' and the 50 top matches are included.</subtitle>
  <link href="https://feedback.vial.today"/>
  <id>pr_a5pnx4kigevnt1k</id>
  <updated>2023-04-04T10:17:21Z</updated>
  <entry>
    <title>make it possible to enter @ in QWERTZ (German) layout</title>
    <link href="https://feedback.vial.today/suggestions/697111/make-it-possible-to-enter-in-qwertz-german-layout"/>
    <id>sug_hqwftudvw7ycndy</id>
    <published>2026-02-27T11:59:46Z</published>
    <updated>2026-03-02T02:01:11Z</updated>
    <content type="text/plain">using foostan Corne 4 trying to set a key to (@) vial gives out (Lsft + 2) which comes out as (").&#13;
Actually multiple special characters (@{}~) don't have any way to be given out correctly.&#13;
&#13;
Some of the characters have other ways to be given out correctly but using the shown input (see attached PNG) they dont work as expeccted.</content>
  </entry>
  <entry>
    <title>Support speculative hold</title>
    <link href="https://feedback.vial.today/suggestions/692323/support-speculative-hold"/>
    <id>sug_laekfffggjcuent</id>
    <published>2026-02-02T08:43:24Z</published>
    <updated>2026-02-09T02:43:33Z</updated>
    <content type="text/plain">Support QMK speculative hold.&#13;
&#13;
Having mod keys held speculatively helps with multi-device input, ex. distinct mouse and keyboard. If an interaction requires a modded mouse input, like shift+left click in GIMP to draw a straight line, or Alt+left drag to move a window, and the mod key is mapped to a dual function key, speculative hold makes the mouse behave as expected instead of making an unmodded click by accident, undoing, and repressing the mod key and awkwardly waiting for the hold timeout.</content>
  </entry>
  <entry>
    <title>Option to default to ISO/JIS as the "Basic" input in the GUI</title>
    <link href="https://feedback.vial.today/suggestions/693368/option-to-default-to-isojis-as-the-basic-input-in-the-gui"/>
    <id>sug_vpcapbcjivzoyni</id>
    <published>2026-02-08T10:04:31Z</published>
    <updated>2026-02-09T02:43:32Z</updated>
    <content type="text/plain">It would be great to have the option to set the ISO/JIS tab as the default "basic" layer. This would be nice for two reasons:&#13;
&#13;
1. The ANSI basic layout doesn't have the KC_NONUS_BSLASH and KC_NONUS_HASH keys, so if the keyboard layout in use relies on this key (e.g. colemak dh iso puts the Z key on KC_NONUS_BSLASH) in can be frustrating having to switch the tab. It's also easier to find the keys when their positions match the layout you are used to.&#13;
&#13;
2. The Vial GUI defaults to the basic tab whenever you click on a key with special tap/hold behavior (e.g. LT(KC), LCtl_T(KC), etc.), so being able to set the "Basic" tab to either ANSI or ISO would reduce the number of clicks.</content>
  </entry>
  <entry>
    <title>Add menus parsing, via supports custom menus</title>
    <link href="https://feedback.vial.today/suggestions/686280/add-menus-parsing-via-supports-custom-menus"/>
    <id>sug_qpsgsbowf4b0to9</id>
    <published>2025-12-30T00:36:00Z</published>
    <updated>2026-01-05T04:00:36Z</updated>
    <content type="text/plain">I hope there can be a feature similar to the menus parsing in via, allowing users to add settings UI for new keyboard functions, which would greatly enhance the extensibility of the keyboard. I also hope that the vial software can add i18n internationalization.</content>
  </entry>
  <entry>
    <title>Automatic VIAL update detection</title>
    <link href="https://feedback.vial.today/suggestions/681799/automatic-vial-update-detection"/>
    <id>sug_yzgm7xhzettnkbu</id>
    <published>2025-12-07T02:12:16Z</published>
    <updated>2025-12-08T02:37:14Z</updated>
    <content type="text/plain">I think it would be neat if VIAL could update on its own or let me know "there is a new update available, would you like to download?" and have it install itself automatically.</content>
  </entry>
  <entry>
    <title>Dip Switch Support in keymap/vial.json</title>
    <link href="https://feedback.vial.today/suggestions/678288/dip-switch-support-in-keymapvialjson"/>
    <id>sug_yxqpwjnvnmgedyf</id>
    <published>2025-11-19T02:26:24Z</published>
    <updated>2025-11-24T06:20:52Z</updated>
    <content type="text/plain">As of right now, there's no way to natively add dip/direct switches in vial. The workaround I was able to figure out was using a "normal matrix", but using a dead column/row for vial to be able to identify the switches, though I don't know how it would work with larger boards that have an encoder with a button connected via direct pin for example, or other special inputs that have a button press.</content>
  </entry>
  <entry>
    <title>Modifier Toggles (aka 'Every-Shot-Modifier')</title>
    <link href="https://feedback.vial.today/suggestions/676507/modifier-toggles-aka-everyshotmodifier"/>
    <id>sug_c9nqprh9kakuqvu</id>
    <published>2025-11-10T05:42:39Z</published>
    <updated>2025-11-17T02:50:43Z</updated>
    <content type="text/plain">I want to make modifier keys such as shift/control/alt have a toggle behavior, like caps lock, on tap.&#13;
&#13;
If you hold them, they are only active for as long as you are holding them, but if you tap them, they become toggled on indefinitely until you tap them again to toggle them off. This differs from one-shot-modifiers in that the modifier will continue being active for every future key stroke.&#13;
&#13;
I'm trying to solve the problem of selecting text while navigating (by word) with arrow keys.&#13;
&#13;
In most applications:&#13;
- `shift` + `right` = expand text selection to the right&#13;
- `ctrl` + `right` = jump to end of word for faster navigation&#13;
However, I don't have enough thumbs to do both. &#13;
I have a momentary layer key which turns my JIKL into arrow keys, and after pressing it I have only 1 thumb left to choose between pressing `shift` or `ctrl`.&#13;
&#13;
The solution to this is simple: make shift have toggle behavior. I can then tap shift on, hold my nav_arrows+ctrl to expand the selection, then shift off.</content>
  </entry>
  <entry>
    <title>Add and remove layers to keymap in GUI</title>
    <link href="https://feedback.vial.today/suggestions/676096/add-and-remove-layers-to-keymap-in-gui"/>
    <id>sug_umiwjfbt7jombpg</id>
    <published>2025-11-07T08:34:46Z</published>
    <updated>2025-11-10T04:20:45Z</updated>
    <content type="text/plain">Add ability to add and remove layers to keymap in GUI.</content>
  </entry>
  <entry>
    <title>Highlight defined macros / tapdance</title>
    <link href="https://feedback.vial.today/suggestions/671082/highlight-defined-macros-tapdance"/>
    <id>sug_jb7gei0utf06olu</id>
    <published>2025-10-09T06:55:25Z</published>
    <updated>2025-10-13T03:04:19Z</updated>
    <content type="text/plain">When defining a new macro / tapdance one must click through all to find s free slot.&#13;
&#13;
Would be great if e.g. a color differentiation on the list of possible ids would hint defined / free slots</content>
  </entry>
  <entry>
    <title>Tap Dance</title>
    <link href="https://feedback.vial.today/suggestions/669103/tap-dance"/>
    <id>sug_joxenmqkhlflu9c</id>
    <published>2025-09-29T18:28:54Z</published>
    <updated>2025-10-06T02:06:41Z</updated>
    <content type="text/plain">Provide ability to configure vial tap dance in initial key map.&#13;
&#13;
I can declare td(0) in my keymap.c but it appears that I cannot set the tap, hold, etc attributes and then have to go into the Vial GUI to do so.&#13;
&#13;
This is confusing and inconsistent.</content>
  </entry>
  <entry>
    <title>Description on hover for macros and  tap dance</title>
    <link href="https://feedback.vial.today/suggestions/669031/description-on-hover-for-macros-and-tap-dance"/>
    <id>sug_csl3gim2k8o5oqg</id>
    <published>2025-09-29T11:05:32Z</published>
    <updated>2025-10-06T02:06:42Z</updated>
    <content type="text/plain">I have full layouts just composed full of TDX and MX. Looking up what is what and changing this is quite cumbersome, especially when the tap dance keys also use macros within.&#13;
&#13;
I constantly jump between keymap-layer, tap dance, and macro tabs back and forth and cycle the definitions within. &#13;
&#13;
It would be very helpful to show the current definition of a tap dance / macro when hovering over them.&#13;
&#13;
Ideally resolving the full chain for also seeing the macro definition within a tap-dance key</content>
  </entry>
  <entry>
    <title>JIS Macro issues</title>
    <link href="https://feedback.vial.today/suggestions/665835/jis-macro-issues"/>
    <id>sug_bcids9uhb9ssb8c</id>
    <published>2025-09-14T00:04:51Z</published>
    <updated>2025-09-15T02:35:07Z</updated>
    <content type="text/plain">When adding macros on Vial to a JIS keyboard, it does not output punctuation properly. I do not know if there is a workaround, but it dampens the utility of macros greatly. for example, if you put a colon in a macro, when pressing that macro, a colon will not come out, and instead a + will.</content>
  </entry>
  <entry>
    <title>More color themese/custom user color themes on the desktop app</title>
    <link href="https://feedback.vial.today/suggestions/664843/more-color-themesecustom-user-color-themes-on-the-desktop-app"/>
    <id>sug_37d6xklnnefjwbn</id>
    <published>2025-09-08T12:05:16Z</published>
    <updated>2025-09-15T02:35:09Z</updated>
    <content type="text/plain">A cosmetic change but something that I feel something that people would want</content>
  </entry>
  <entry>
    <title>Add comments</title>
    <link href="https://feedback.vial.today/suggestions/657850/add-comments"/>
    <id>sug_psituamwygil0sr</id>
    <published>2025-07-31T04:30:18Z</published>
    <updated>2025-08-04T04:01:53Z</updated>
    <content type="text/plain">Add the ability to comment on the layout. For example, using a separate text file in the following format:&#13;
layer:key: "comment"&#13;
Also, add the ability to comment on the entire layer.</content>
  </entry>
  <entry>
    <title>Allow for multiple keys to be selected for remapping</title>
    <link href="https://feedback.vial.today/suggestions/643058/allow-for-multiple-keys-to-be-selected-for-remapping"/>
    <id>sug_pnh2ycfdbsz7ets</id>
    <published>2025-05-24T06:46:40Z</published>
    <updated>2025-05-26T02:54:55Z</updated>
    <content type="text/plain">I think it would benefit the usability of the VIAL GUI were it possible to select multiple keys to remap. For example, allowing the selection of a whole row of keys to remap to transparent for a layer. It can be a little annoying having to repeatedly click to remap to the same key. I know that VIAL auto-selects the next key in a row, but sometimes there are situations where you want to apply a mapping to multiple non-sequential keys. &#13;
&#13;
Ideally this would work by holding CTRL to select multiple keys, and left clicking without CTRL would deselect everything else, similar to how it works in most programs. Keyboard Layout Editor is probably the most similar example. Maybe a drag to select feature would work too, similar to KLE, although I understand that might take a lot of extra effort to implement. &#13;
&#13;
Thank you for taking the time to read my suggestion.</content>
  </entry>
  <entry>
    <title>I wish when recording a macro you could record a delay and set the number of times the macro loops.</title>
    <link href="https://feedback.vial.today/suggestions/625182/i-wish-when-recording-a-macro-you-could-record-a-delay-and-set-the-number-of-tim"/>
    <id>sug_zjnfjgnw6q5x7yw</id>
    <published>2025-03-30T13:57:05Z</published>
    <updated>2025-03-31T02:56:02Z</updated>
    <content type="text/plain">I found that when recording macros with VIAL, you cannot record delay at the same time. You need to add delay instructions manually, which is annoying. And VIAL does not support setting the number of macro loops, or infinite loops. I hope these bugs can be fixed.</content>
  </entry>
  <entry>
    <title>support VIA V3 protocol</title>
    <link href="https://feedback.vial.today/suggestions/621419/support-via-v3-protocol"/>
    <id>sug_jxgnwhldaag53ji</id>
    <published>2025-03-14T16:34:01Z</published>
    <updated>2025-03-17T03:15:09Z</updated>
    <content type="text/plain">per title. allow V3 protocol support.</content>
  </entry>
  <entry>
    <title>Include Apple silion ARM CPU binaries in releases (M1, M2, M3, M4)</title>
    <link href="https://feedback.vial.today/suggestions/617497/include-apple-silion-arm-cpu-binaries-in-releases-m1-m2-m3-m4"/>
    <id>sug_kh4hdzkul2geggv</id>
    <published>2025-02-26T20:05:57Z</published>
    <updated>2025-03-03T02:42:25Z</updated>
    <content type="text/plain">Currently only Intel x86 binaries are provided which will not run on recent Apple computers without the Rosetta emulation software installed.</content>
  </entry>
  <entry>
    <title>would be nice to assign color to layers</title>
    <link href="https://feedback.vial.today/suggestions/616484/would-be-nice-to-assign-color-to-layers"/>
    <id>sug_kntbiz5m77n1mo0</id>
    <published>2025-02-21T21:37:05Z</published>
    <updated>2025-02-24T02:36:12Z</updated>
    <content type="text/plain">when I switch layers I would like the color of my keyboard to change. this does not seem to be an option</content>
  </entry>
  <entry>
    <title>a Macro containing (layer) does not work</title>
    <link href="https://feedback.vial.today/suggestions/616483/a-macro-containing-layer-does-not-work"/>
    <id>sug_85fde0sba7q8hku</id>
    <published>2025-02-21T21:36:01Z</published>
    <updated>2025-03-03T02:42:25Z</updated>
    <content type="text/plain">For some reason when putting a layer inside a macro it does not work.</content>
  </entry>
  <entry>
    <title>Arabic Language Layout</title>
    <link href="https://feedback.vial.today/suggestions/614927/arabic-language-layout"/>
    <id>sug_nx6ngfzyfq02h4a</id>
    <published>2025-02-15T18:14:04Z</published>
    <updated>2025-02-17T08:34:54Z</updated>
    <content type="text/plain">Hi there,&#13;
&#13;
I wish I can see an Arabic language layout soon on Vial. Arabic language has 28 letters and Tashkeel is something else! You may look it up if you're curious!&#13;
&#13;
I am new to ergonomic keyboards in general, and the first step for me was Corne v4, which runs on Vial. It's been amazing what I can do with the keyboard and how comfortable could it be!&#13;
&#13;
But since nothing in this world is an infinite happy story, I came across the issue I mentioned above. Arabic is my mother tongue, and it has 28 letters and other symbols that may change the words meanings (Please check the attachment). I hope I can see an Arabic Layout in Vial, actually, I don't know if there is a team working on it, I know very little about GitHub and the open-source thing, and I am making my way through programming (Just beginning!). But if this is a project, I'd love to help, really! It'll make me learn faster.&#13;
&#13;
Thank you all!&#13;
Regards,&#13;
&#13;
Yzn</content>
  </entry>
  <entry>
    <title>Add Mac specific symbols to editor</title>
    <link href="https://feedback.vial.today/suggestions/611466/add-mac-specific-symbols-to-editor"/>
    <id>sug_4hhztjhgk9fe3ga</id>
    <published>2025-01-31T08:13:55Z</published>
    <updated>2025-02-03T05:42:40Z</updated>
    <content type="text/plain">Hello!&#13;
It would be nice to have all the mac specific symbols/names in the editor.&#13;
For example, Command instead of left/right GUI, Option instead of left/right ALT and so on.&#13;
This should probably be independent of the keyboard layout/language selection.</content>
  </entry>
  <entry>
    <title>Improve Home Row Modifiers</title>
    <link href="https://feedback.vial.today/suggestions/607627/improve-home-row-modifiers"/>
    <id>sug_n6ry0lvg7ws18o4</id>
    <published>2025-01-17T20:44:28Z</published>
    <updated>2025-01-20T04:42:27Z</updated>
    <content type="text/plain">I have recently acquired a VIAL adapter from Epomaker. When transitioning from software based solutions like keyd and Kanata I have struggled to achieve the same level of precision my home row modifiers implementation has using the aforementioned tools. The QMK and VIAL communities have attempted to address this with libraries like Achordion. But I think HRMs, being such a widely adopted pattern, should have a first class, out-of-the-box useable implementation. Typing streaks, bilateral combinations and repeat-on-timeout are some of the improvements I believe are missing. In essence, I don't think we should settle with users having to adapt to the current limitations and significantly change their natural way of typing to benefit from HRMs.</content>
  </entry>
  <entry>
    <title>support bilateral combinations</title>
    <link href="https://feedback.vial.today/suggestions/598763/support-bilateral-combinations"/>
    <id>sug_wqpv7wytcora2x6</id>
    <published>2024-12-10T09:04:41Z</published>
    <updated>2025-01-20T04:42:27Z</updated>
    <content type="text/plain">please add "bilateral combinations" which allow to use home row mods only on the opposite hand.&#13;
https://github.com/qmk/qmk_firmware/pull/17715&#13;
https://sunaku.github.io/home-row-mods.html</content>
  </entry>
  <entry>
    <title>Let vial support wireless.</title>
    <link href="https://feedback.vial.today/suggestions/596948/let-vial-support-wireless"/>
    <id>sug_v67b2o6rbst0fdd</id>
    <published>2024-11-30T07:22:32Z</published>
    <updated>2024-12-02T03:38:03Z</updated>
    <content type="text/plain">You can take a look at my branching code.：https://github.com/KeyDreamLin/qmk_firmware&#13;
This is just a serial port  to wireless chip。&#13;
Currently, dual mode is supported。&#13;
If you need a sample of my wireless chip. You can contact me。&#13;
I am very eager to make vial  support wireless, and wireless modification keycode!&#13;
I can assist vial members in porting serial protocols.</content>
  </entry>
  <entry>
    <title>Automatically switch key layers</title>
    <link href="https://feedback.vial.today/suggestions/593558/automatically-switch-key-layers"/>
    <id>sug_rj7rz2x0fu7ejvm</id>
    <published>2024-11-14T02:41:14Z</published>
    <updated>2024-12-02T03:38:03Z</updated>
    <content type="text/plain">It's useful to have a feature that monitors the active window and automatically switches to the appropriate key layer.&#13;
A device called TourBox has this feature.</content>
  </entry>
  <entry>
    <title>Can I use custom key codes with key overrides?</title>
    <link href="https://feedback.vial.today/suggestions/593557/can-i-use-custom-key-codes-with-key-overrides"/>
    <id>sug_qbdapwwkbmldyjg</id>
    <published>2024-11-14T02:33:11Z</published>
    <updated>2024-12-02T03:38:03Z</updated>
    <content type="text/plain">Even if I set a custom key code in the Replacement of Key Overrides, it doesn't work.&#13;
Is this a specification of QMK Firmware?</content>
  </entry>
  <entry>
    <title>Add a way to cancel the security unlock</title>
    <link href="https://feedback.vial.today/suggestions/592503/add-a-way-to-cancel-the-security-unlock"/>
    <id>sug_mv7smmev8bqqrlz</id>
    <published>2024-11-08T13:04:57Z</published>
    <updated>2024-11-11T04:45:59Z</updated>
    <content type="text/plain">Currently when trying to use Matrix tester you have to unlock the keyboard (Which is good!) But the keyboard may not function correctly yet, as that's what you want to use the matrix tester for. If one of the unlock buttons for example doesn't work there is no way to cancel the unlock operation and you have to force close the application using task manager or similar. I feel like a cancel button could solve this easily.</content>
  </entry>
  <entry>
    <title>Arbitrary Unicode mapping</title>
    <link href="https://feedback.vial.today/suggestions/577079/arbitrary-unicode-mapping"/>
    <id>sug_lctmbq5eywvil9b</id>
    <published>2024-08-24T00:42:01Z</published>
    <updated>2024-08-26T02:09:15Z</updated>
    <content type="text/plain">I would like to be able to map. I used to use a MacBook and got very used to being able to quickly type common Unicode (see https://www.lifewire.com/how-to-use-alt-codes-4768659#:~:text=Press%20Option%20to). Since most Unicode are not in the menus (with the exception of Yen and some others, and I can't find a function for it).</content>
  </entry>
  <entry>
    <title>Add generic naming for custom functions like layers, combos, macros, tap dance, etc...</title>
    <link href="https://feedback.vial.today/suggestions/575385/add-generic-naming-for-custom-functions-like-layers-combos-macros-tap-dance-etc"/>
    <id>sug_4qgujonb5ujgovx</id>
    <published>2024-08-16T23:36:37Z</published>
    <updated>2024-08-19T02:28:45Z</updated>
    <content type="text/plain">Trying to remember what combo sixteen was doing with tap dance ten is hard to remember after a few months, it would be nice to be able to name each of those things to easily edit them later on.</content>
  </entry>
  <entry>
    <title>Human-understandable UI</title>
    <link href="https://feedback.vial.today/suggestions/564834/humanunderstandable-ui"/>
    <id>sug_n6foidwew8x1krk</id>
    <published>2024-07-05T01:43:53Z</published>
    <updated>2024-07-08T03:58:40Z</updated>
    <content type="text/plain">Currently UI is esoteric with all these abbreviations and random key names like TD(0) or Bskp. It would be nice to have UI refactored so that people could understand it without reading manuals and google first. It would allow non-tech people to use the application. I understand that these things were named so that they would fit the keys, but outside of the keyboard layout we could use human-readable names, such as Backspace, Macro1, CapsLock and Row2Column3 for generic names.</content>
  </entry>
  <entry>
    <title>[Feature Request] Heat-map generator</title>
    <link href="https://feedback.vial.today/suggestions/563280/feature-request-heatmap-generator"/>
    <id>sug_hj7aagkmub8zjgv</id>
    <published>2024-06-27T07:10:36Z</published>
    <updated>2024-07-01T03:19:47Z</updated>
    <content type="text/plain">Hey! &#13;
&#13;
Thanks for an awesome app and functions. &#13;
&#13;
I have a trouble that when trying to generate a heatmap there are many steps that are required. &#13;
Especially some are a duplication of much information that Vial App already have available to it. &#13;
&#13;
In my feable mind the Vial App is capable of generating heat-maps. &#13;
&#13;
1. It has a picture of the layout&#13;
2. a representation of the matrix&#13;
3. A link between the matrix and the picture (Matrix tester) &#13;
4. It's already capable of logging key presses.&#13;
&#13;
Then what's then missing?&#13;
To me, not knowing the intricacies, the actual heat-map generation of making more keypresses "red" and leaving the other transparent and green... But...? - I'm sure I don't see the elephant obstacle to make this happen? &#13;
&#13;
In my mind the generation of heatmaps could/should happen over time and slow develop "as you go". And not like the qmk-generator online that gives you the picture in one go.&#13;
How possible is this feature and are there anyone else interested in this function?</content>
  </entry>
  <entry>
    <title>Keybinds for API triggers</title>
    <link href="https://feedback.vial.today/suggestions/558578/keybinds-for-api-triggers"/>
    <id>sug_k8gb7cxjyf17niu</id>
    <published>2024-06-04T09:03:13Z</published>
    <updated>2024-06-10T02:01:42Z</updated>
    <content type="text/plain">Currently, user is limited to use keys available in the standard keymap on every OS, which is limiting when implementing for example a macropad. Some may use additional key combinations, but they may often conflict with user holding a specific key down while using macropad + has other limitations when trying to combine macros together.&#13;
&#13;
Add a special keycode that will not trigger any keypress, but instead it'll output specific message to the rawhid endpoint that a specific key was pressed. Options for the exact message are:&#13;
&#13;
user-specified code or message, assigned to the key with the mentioned above keycode&#13;
Position of the pressed key on the matrix + optionally current layer&#13;
&#13;
This way, any software allowed to listen on the rawhid endpoint can react to those special events and implement any desired functionality this way, without conflicting with any keypressed handled by OS or other software. If nothing listens on the endpoint, keys will simply do nothing</content>
  </entry>
  <entry>
    <title>Ability to "LABEL" keys</title>
    <link href="https://feedback.vial.today/suggestions/547376/ability-to-label-keys"/>
    <id>sug_szzn6uz6ylfwhvk</id>
    <published>2024-04-23T00:08:21Z</published>
    <updated>2024-04-29T02:01:40Z</updated>
    <content type="text/plain">When programming a macropad with a large number of keyboard shortcuts it is extremely useful to be able to LABEL the keys, not just see the actual key codes that are attached to a key.  For example SHIFT+ALT+UP ARROW might be "LAYER UP". It would be great to be able to simple assign a label that is displayed in the GUI on the key.  Although some of this functionality can be acheived using custom keycodes this is not simple and not a practical method for labelling hundreds of keys / keyboard shortcuts.</content>
  </entry>
  <entry>
    <title>Ability to swap key locations / assignments.</title>
    <link href="https://feedback.vial.today/suggestions/547374/ability-to-swap-key-locations-assignments"/>
    <id>sug_goxgwhzt6mqzw42</id>
    <published>2024-04-23T00:01:55Z</published>
    <updated>2024-04-29T02:01:40Z</updated>
    <content type="text/plain">This feature request has some crossover with the "drag and drop keys" request...&#13;
&#13;
When programming a macropad to work with an applications various keyboard shortcuts (photoshop, etc) and assigning them locations on a macropad, it is extremely useful to be able to SWAP the location of two keys.</content>
  </entry>
  <entry>
    <title>Add names for Macros</title>
    <link href="https://feedback.vial.today/suggestions/545833/add-names-for-macros"/>
    <id>sug_qcheqcystwcx316</id>
    <published>2024-04-14T09:59:40Z</published>
    <updated>2024-04-15T23:12:59Z</updated>
    <content type="text/plain">macros can have names that can be displayed in the GUI when you assign them to buttons, When we configure many macros, its very confusing when figuring out what is assigned to what.</content>
  </entry>
  <entry>
    <title>Record macros in Vial MacOS</title>
    <link href="https://feedback.vial.today/suggestions/543697/record-macros-in-vial-macos"/>
    <id>sug_z4q5felmneprbbe</id>
    <published>2024-04-05T12:34:52Z</published>
    <updated>2024-04-08T02:01:44Z</updated>
    <content type="text/plain">This feature is missing on the Vial MacOS app.</content>
  </entry>
  <entry>
    <title>Hold the key down, the layer is activated and the KC long pressed.</title>
    <link href="https://feedback.vial.today/suggestions/542571/hold-the-key-down-the-layer-is-activated-and-the-kc-long-pressed"/>
    <id>sug_9tmw5rkb7szmltz</id>
    <published>2024-03-31T10:05:15Z</published>
    <updated>2024-04-01T04:03:17Z</updated>
    <content type="text/plain">Hold the key down, the layer is activated and the KC long pressed.&#13;
It  is mainly used for “Alt + TAB (switch windows) ”</content>
  </entry>
  <entry>
    <title>Allow nested modifiers in Quantum section</title>
    <link href="https://feedback.vial.today/suggestions/535005/allow-nested-modifiers-in-quantum-section"/>
    <id>sug_7vop4dj80gabv0u</id>
    <published>2024-02-21T13:27:27Z</published>
    <updated>2024-02-26T17:28:47Z</updated>
    <content type="text/plain">For example I would like to make a combination like LALT_T(LCTL(KC_Z)) - that is Ctrl+Z on tap and "Left Alt" on Hold. &#13;
Currently this combination is always changed to LALT_T(KC_Z)&#13;
BTW: using Vial 0.7.1 with Cyboard Dactyl Keyboard</content>
  </entry>
  <entry>
    <title>Option to open softwares from computer.</title>
    <link href="https://feedback.vial.today/suggestions/520720/option-to-open-softwares-from-computer"/>
    <id>sug_coirltmwnxski9r</id>
    <published>2024-01-10T16:11:16Z</published>
    <updated>2024-01-16T01:11:42Z</updated>
    <content type="text/plain">While adding vial support to macro pads, it will be very useful if we have an option to start an application. So we can choose a key and select an application. We can choose the exe [ In the case of Windows] and on button press, this application will run.</content>
  </entry>
  <entry>
    <title>Combo mapping with auto-advance</title>
    <link href="https://feedback.vial.today/suggestions/518303/combo-mapping-with-autoadvance"/>
    <id>sug_8ojdzrw3vhalmz9</id>
    <published>2023-12-31T10:10:54Z</published>
    <updated>2024-01-01T02:39:25Z</updated>
    <content type="text/plain">When mapping a combo, the focus does not auto-advance to the next combo-key, like with normal key-mapping. This would make mapping a lot faster and easier.&#13;
Same for Tap-Dance</content>
  </entry>
  <entry>
    <title>Add Enable on Layers Option to Combos</title>
    <link href="https://feedback.vial.today/suggestions/518207/add-enable-on-layers-option-to-combos"/>
    <id>sug_weu8zkysxqntvdp</id>
    <published>2023-12-30T19:37:52Z</published>
    <updated>2024-01-01T02:39:25Z</updated>
    <content type="text/plain">Suggest adding layer option for combos so that the same combos can perform different actions on different layers. This would be useful when mac and pc shortcuts are not aligned.</content>
  </entry>
  <entry>
    <title>Modifier key delay support</title>
    <link href="https://feedback.vial.today/suggestions/505990/modifier-key-delay-support"/>
    <id>sug_1yes1mqj5qykoyr</id>
    <published>2023-11-03T06:10:49Z</published>
    <updated>2023-11-06T14:45:55Z</updated>
    <content type="text/plain">Modifier keys seem to default to 0 delay,i've found that a lot of software doesn't accurately recognize whether a modifier key has been triggered,because 0 delay is too fast.This is a very serious problem,the usefulness of modifier keys is severely reduced.This can be fixed if the modifier keys support adding delays or changing the default 0 delay to 50ms or 100ms.</content>
  </entry>
  <entry>
    <title>Layer Names in EEPROM</title>
    <link href="https://feedback.vial.today/suggestions/497679/layer-names-in-eeprom"/>
    <id>sug_pymyse53u730cc7</id>
    <published>2023-09-30T22:30:34Z</published>
    <updated>2023-09-30T22:34:21Z</updated>
    <content type="text/plain">I'd love to be able to have names for layers rather than just 0/1/2/3 etc.&#13;
It would make learning and sharing layouts between customers much, much easier.  It's a very nice feature in Oryx, and with the complete lack of memory constraints in modern MCUs seems more reasonable than ever.&#13;
Seems like it would just require saving/retrieving layer names in EEPROM?</content>
  </entry>
  <entry>
    <title>Move Mod Tap keycodes to a separate tab, named 'Mod Tap'</title>
    <link href="https://feedback.vial.today/suggestions/497167/move-mod-tap-keycodes-to-a-separate-tab-named-mod-tap"/>
    <id>sug_03sayg7ofntmsv5</id>
    <published>2023-09-29T08:25:19Z</published>
    <updated>2023-09-30T22:34:03Z</updated>
    <content type="text/plain">As it is now, they are 'hidden' under the unfamiliar 'Quantum' tab, that no new user fully understands what it does, and rarely dares to enter and browse.&#13;
&#13;
Instead they end up using Tap Dance to re-invent the wheel all over. &#13;
&#13;
I think if the two tabs were split, it would make more sense, and the name on that tab would better guide users to the functions they are needing, vs the hard to understand 'Quantum'.</content>
  </entry>
  <entry>
    <title>Support for Croatian key previews</title>
    <link href="https://feedback.vial.today/suggestions/493852/support-for-croatian-key-previews"/>
    <id>sug_bxhfujva94lrofa</id>
    <published>2023-09-21T17:04:47Z</published>
    <updated>2023-09-25T03:55:35Z</updated>
    <content type="text/plain">It would be great if Vial supported the Croatian keyboard layout. The EurKey layout cannot be used to input the Croatian characters č, ć, š and ž. It only supports đ. It would also be useful for people from Bosnia, Serbia and Montenegro as they could also write in their native language (the Latin script).&#13;
&#13;
Let me know if that sounds good. I't be happy to help in adding it in any way. I looked around the project repository but couldn't really figure out where to start and how I would add it.&#13;
&#13;
Check the image to see how I am doing it right now :)</content>
  </entry>
  <entry>
    <title>Please add Colemak and Dvorak base keyboard layouts</title>
    <link href="https://feedback.vial.today/suggestions/492800/please-add-colemak-and-dvorak-base-keyboard-layouts"/>
    <id>sug_r6fnbpdtnga1l5e</id>
    <published>2023-09-19T02:27:41Z</published>
    <updated>2023-09-25T03:55:35Z</updated>
    <content type="text/plain"/>
  </entry>
  <entry>
    <title>layer indication as a system tray icon.</title>
    <link href="https://feedback.vial.today/suggestions/489652/layer-indication-as-a-system-tray-icon"/>
    <id>sug_quqnnqkasjl6e4s</id>
    <published>2023-09-10T15:06:59Z</published>
    <updated>2023-09-11T04:11:27Z</updated>
    <content type="text/plain">Could a system tray icon be added to indicate what layer the keymap is currently on? Either with a number or a color? Maybe an open option could be added to it with a right click.</content>
  </entry>
  <entry>
    <title>Combo Reference Per Layer</title>
    <link href="https://feedback.vial.today/suggestions/483331/combo-reference-per-layer"/>
    <id>sug_rjugrsopsu66m0o</id>
    <published>2023-08-29T21:25:29Z</published>
    <updated>2023-09-03T20:59:47Z</updated>
    <content type="text/plain">make vial's combos be able to use combo_ref_from_layer callback</content>
  </entry>
  <entry>
    <title>highlight used keys</title>
    <link href="https://feedback.vial.today/suggestions/481325/highlight-used-keys"/>
    <id>sug_9gj60eb1amsevhk</id>
    <published>2023-08-26T21:31:25Z</published>
    <updated>2023-08-28T03:13:00Z</updated>
    <content type="text/plain">It would be nice if keys used at least once in a layer were highlighted in the bottom palette. This would make it easier to know which keys were not yet accounted for when starting a new layout. Maybe this could be enabled/disabled in a menu, but there's no menu for preferences.</content>
  </entry>
</feed>
