Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Better custom keycode process #8

Open
nivekmai opened this issue Dec 3, 2024 · 0 comments
Open

Better custom keycode process #8

nivekmai opened this issue Dec 3, 2024 · 0 comments

Comments

@nivekmai
Copy link
Contributor

nivekmai commented Dec 3, 2024

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant