You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Saw your writeup and the issue you were (maybe) facing trying to put in custom keycodes into your keymap. I think I found a better way to do it that avoids merge conflicts by using macros in the worst way possible.
If you make a macro to "remap" a key, you can make Oryx generate a keymap that uses your custom keycode:
keymap.c
#define KC_F24 QK_REPEAT_KEY
// ...rest of the keymap file
#undef KC_F24
So now basically whenever there's KC_F24 in the keymap file, it's actually QK_REPEAT_KEY, so you won't get merge conflicts (and, you can place F24 wherever you want to move QK_REPEAT_KEY easily).
Saw your writeup and the issue you were (maybe) facing trying to put in custom keycodes into your keymap. I think I found a better way to do it that avoids merge conflicts by using macros in the worst way possible.
If you make a macro to "remap" a key, you can make Oryx generate a keymap that uses your custom keycode:
So now basically whenever there's
KC_F24
in the keymap file, it's actuallyQK_REPEAT_KEY
, so you won't get merge conflicts (and, you can place F24 wherever you want to moveQK_REPEAT_KEY
easily).Example
The text was updated successfully, but these errors were encountered: