Open lesca opened 1 year ago
Hello, this is a issue I found that makes custom HEX keycodes very difficult to reuse.
0x7C70
QK_DYNAMIC_TAPPING_TERM_PRINT
KC_NO
Note: in JSON file, it shows as 0x7c70 correctly.
0x7c70
I expect the app can respect the HEX codes. The codes works perfectly if I type them manually within ANY, and it can be exported successfully.
ANY
I create this issue to track. Thanks for your attention.
Regards, Lesca
I also need fix that
Hello, this is a issue I found that makes custom HEX keycodes very difficult to reuse.
Current Behavior:
0x7C70
forQK_DYNAMIC_TAPPING_TERM_PRINT
which is currently not supported by VIA.0x7C70
now becomeKC_NO
Note: in JSON file, it shows as
0x7c70
correctly.Expected Behavior
I expect the app can respect the HEX codes. The codes works perfectly if I type them manually within
ANY
, and it can be exported successfully.I create this issue to track. Thanks for your attention.
Regards, Lesca