Adding custom keymap.c code for key overrides #279
-
I'm using this from the qmk guide to try to add the simple delete override example to my miryoku layout in this repo. all of my layout changes so far have been in users -> custom_config.h. based on the customisation documentation, ive copied across the files from layouts -> config.h and keymap.c to keyboards -> keymaps. i added
did i place the rule in the wrong file? or the example code? thanks |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
I think the issue I was having here is related to mixing keyboard keymap.c and user keymap.c (manna-harbour_miryoku.c). Since adding my overrides to the latter I've managed to get at least one override to work. |
Beta Was this translation helpful? Give feedback.
-
The customisation docs recommend using the keyboard keymap.c for custom hardware support. Customising the keymap outside of what's supported by custom_config.h isn't described yet. The plan is to add a custom_keymap.c for that purpose. However, certain keymap features may only work when in the same file as the actual keymap, so that may not be a general solution. For now, arbitrary keymap customisations will need be made in manna-harbour_miryoku.c and manna-harbour_miryoku.h. For key overrides in particular, as they are already in use they will need to be incorporated there. In future, support could be added so additions can be declared in custom_config.h. |
Beta Was this translation helpful? Give feedback.
The customisation docs recommend using the keyboard keymap.c for custom hardware support. Customising the keymap outside of what's supported by custom_config.h isn't described yet.
The plan is to add a custom_keymap.c for that purpose. However, certain keymap features may only work when in the same file as the actual keymap, so that may not be a general solution.
For now, arbitrary keymap customisations will need be made in manna-harbour_miryoku.c and manna-harbour_miryoku.h.
For key overrides in particular, as they are already in use they will need to be incorporated there. In future, support could be added so additions can be declared in custom_config.h.