Open cocoabox opened 1 year ago
Same thing here, It seems that any keyup/keydown sequence is rejected by the macro editor.
MS Edge 120.0.2210.133, Windows 11
This seems to be happening for any keydown/keyup. I tried to do Alt+0163 for the pound sterling symbol and it complains about invalid keycode KC_LALT
{+KC_LALT}{KC_P0}{KC_P1}{KC_P6}{KC_P3}{-KC_LALT}
The workaround I'm following for now is to use the Windows on-screen keyboard to type the shortcut out while VIA is in recording mode. The code that it records in the textbox is exactly the same.
same here
is there yet a solution on the way ?
interested in fix also
Any updates here? Im still suffering
okay, found a workwaround. For example you want a macro to change keyboard layout on MacOS, which is CTRL+Space
while recording press and release ctrl, then press and release Space and once again press ctrl and release. You will get something like this
Then remove extra key states by clicking X on top of the keys, so it will look like this
Same issue here. Just trying to create a macro to write ">" and "<" on AZERTY keyboard but I just can't figure out a way to make it work... Pretty annoying bug
Same issue here. Just trying to create a macro to write ">" and "<" on AZERTY keyboard but I just can't figure out a way to make it work... Pretty annoying bug
I just found the solution, you have tu use NUBS
special character to write "<" and use Shift with that key to write ">"
Describe the bug Captured these keys which generated the following sequence
and tried to use this sequence on another macro
Just to get a "Whoops Invalid keycode detected inside {} +KC_LGUI
To Reproduce Steps to reproduce the behavior:
Expected behavior VIA app should accept the copy/pasted sequence
Screenshots see above
VIA Version
Keyboard firmware VIA protocol 9
Desktop (please complete the following information):
Custom json definition?
Sanity checks
Additional context Add any other context about the problem here.