Skip to content

Better custom keycode process #8

@nivekmai

Description

@nivekmai

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).

Example

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions