Please clarify the limitations of "Any" key.

[kiprou]

The Special > Any key offers infinite possibilities when working directly with QMK.

But it seems that when using VIA we're limited to just the options in this menu:

For instance, keycodes like S(KC_H) and C(A(KC_DEL)) simply don't work, despite the fact that they follow the same syntax as the VIA menu and QMK docs.

I don't expect full QMK functionality inside VIA, but is it really true that S(KC_1) works and S(KC_H) doesn't?

It's difficult to find information about this online, so perhaps I'm mistaken.

Currently using https://usevia.app/ to configure an EPOMAKER EK21. Thanks for the friendly app!

[joonhyuk]

+1 on CIDOO V21 (brother of EK21)

[raulfunkie]

Not sure if this was fixed recently, or it has been like this for the longest time, but you just need to write the keycode and that’s it.

For example:

• You can assign Any to the Key you want to map
• When the modal comes up just type S(KC_H) (or whatever other keycode you want, really).
• For reference I’ve used similar to LCAG(KC_H)
• You can find a good list of modifiers here.

[kiprou]

Sorry for not being clear: I know how to find and write the desired keycodes, my issue is that they don't work unless they're already listed in VIA's dropdown menu. It's as if those are the only codes that VIA has implemented or something. If I try other codes, it will save them to the key, like, as a legend or whatever, but it won't actually work in practice when I press it.

However, my EK21 keypad only has VIA support and not full QMK support, so perhaps that's the issue. I have no idea.

Are you saying that S(KC_H) works for you on the Any key? If so, what keyboard/keypad do you use? And does it have full QMK support?

[qtov]

I'll also say that LT(1,KC_SPACE) works, because it's also present in "LAYERS" under "SPACE Fn1", but when I try to make it LT(1,KC_ESC) from the ANY key, it simply doesn't work.

I don't really understand why it is like this, it makes absolutely no sense.

Edit: Apparently, it's a poorly implemented via support from the manufacturer, which makes this weird behavior, ignore my comment.

[ericmburgess]

Edit: It seems like the confirm button enables again once you have typed (part of?) a valid QMK code.

Just 11 days ago, I was able to enter arbitrary QMK codes in the web app. But today, I'm having the same problem mentioned in this issue--I have the options available in the dropdown, and that's it. I can type whatever I want, but the confirm button is disabled.

[keiohtani]

+1