Tap-Hold support?

[a9udn9u]

Is there plan to support configuring tap-hold keys?

[Pastitas]

I am also interested in this, is there any intention of supporting all features from qmk? i'm specifically interested in the Modifier Keys with the fuction while holding and another when tapped, LALT(kc) and so. If not, what would be necesary to make it work?

[olivavek]

I'm also interested in this feature.

[pingshunhuangalex]

It's kinda supported already. You can use the Any in the special key section and use mod-tap function directly.

Don't forget to use the MT() instead of shortcut or aliases as they may not be supported in some cases (https://docs.qmk.fm/#/mod_tap?id=caveats).

[aegatlin]

@pingshunhuangalex thank you for pointing out the Any special key. That is such a powerful key/feature I wonder if it would be beneficial to call it out in the docs? As a new user to Via, I was about to sadly move on to editing raw QMK source code (yet again) because I didn't realize what Any really was. Now I'm excited to continue using Via. On the off-chance other new users are like me, mentioning the power of Any somewhere early in the docs or website could help.

Thank you, and excited to continue using Via :D

[ctconwell]

Reviving this thread to say that I wish VIA could configure tap-hold time, or TAPPING_TERM in the QMK config file. I have a CIDOO/Finalkey V65 V2 and use Space Fn1 almost exclusively to access layer 1. However, for whatever reason, the default tap-hold time on this keyboard seems shorter than my others (also flashed with VIA), so I end up missing a lot of space keystrokes. Re-flashing this board with VIAL has been challenging because I can't get it to enter bootloader mode. To have this option in VIA would be really powerful.

[trustednstaller]

Experiencing similar issues. They key that is supposed to get triggered on hold, gets triggered on a tap a majority of the time, unless I do it slowly. This is absurd. Also the Any key is simply not flexibly enough when it comes to modifiers. There shouldn't be a limit on the tap/hold functionality to a limited set of keys. It should apply to all keys. There is a LALT (hold) ( (tap) key. Why? If you can do this, you should allow the capacity for any key. It is so difficult to get used to VIA on my Ferris coming from a PLANCK. If all this can be done in the source code, please anyone direct me to the right code/docs etc. Wouldn't mind doing this.

[oc-tk]

I have same problem. I would like to bind some keys together, for example Enter and Win key and Any key just does not allow me to insert this value :C

[martin-braun]

It's kinda supported already. You can use the Any in the special key section and use mod-tap function directly.

Don't forget to use the MT() instead of shortcut or aliases as they may not be supported in some cases (docs.qmk.fm/#/mod_tap?id=caveats).

It doesn't work for me on the Keychron K7 Pro, because the UI won't accept my input:

Why is "Confirm" greyed out, please? I already disabled fast key mapping without success.

EDIT: Ok I figured it out. To enable another layer when holding a key, I have to use the LT function.

So instead of MT(MO(3), KC_ESC) I have to use LT(3, KC_ESC).

Nice.

[Rizautomo]

I have similar issue with this. My board is local board from Indonesia which using json file to load the through via definitions. Even tho I'm writing using Any on via and it written well (got some evidence on via ui accepting the qmk code), seems layer tap and mod tap doesnt support with this current version of this board json file. #

on the key tester tabs, the qmk writing doesnt tell the keyboard anything to do