search

the-via / releases

GNU General Public License v3.0
1.99k stars 222 forks source link

VIA app macro editor says "whooops invalid keycode" even for captured codes. #273

Open cocoabox opened 9 months ago

cocoabox commented 9 months ago

Describe the bug Captured these keys image which generated the following sequence

{+KC_LGUI}{+KC_F2}{-KC_LGUI}

and tried to use this sequence on another macro

image

Just to get a "Whoops Invalid keycode detected inside {} +KC_LGUI

To Reproduce Steps to reproduce the behavior:

  1. Go to M0, click Fullscreen, click ● record
  2. press CMD + F2 , release release ; click Stop, click Save
  3. Go to </> to get the keycode sequence. copy the sequence to clipbrd
  4. Go to M1, go to </> and paste .
  5. VIA app yells "Whoops Invalid keycode detected inside {} +KC_LGUI

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.

nimro commented 5 months 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

image

mendhak commented 4 months ago

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.

martin-bertele commented 2 months ago

same here

is there yet a solution on the way ?

ka2er commented 2 months ago

interested in fix also