Question for all you #QMK and #MechanicalKeyboards lovers out there: the ErgoDash default layout has a couple of C functions in the keymap file. Do I need (to keep) them?
I'm playing with my keymap for the first time, while waiting for my ErgoDash to arrive.
I've created a few layers and everything compiles. ✌🏻
I don't want to brick the #keeb as soon as it arrives, so I was trying to understand what those functions are for.
@ajwk
I actually was thinking to rename those keycodes a bit differently (QWERTY, RIGHT, LEFT, MOUSE, and MODDH), but, if I properly understood, if I use, say, MO(1) instead of MO(RIGHT) to activate a layer, everything should work fine, right?
@AAMfP The argument to MO() is a layer number, not a keycode. Notice that the default/keymap.c defines two enums at the top: one for the layers, and one for the custom keycodes (starting from SAFE_RANGE). But yes, you can just use MO with your own layer numbers in your keymap, and skip all the tri-layer stuff that the default keymap does with its custom keycodes.
@AAMfP Correction: ‘persistent_default_layer_set’ does not appear to be used at all. The ‘process_record_user’ function is using ‘set_single_persistent_default_layer’ (a function provided by QMK’s quantum.c) instead.
@AAMfP
Not 100% sure, but if you don't know what they are and they don't take too much on board memory then leave the functions. I do think though if you can figure out what purpose they have and you don't need them then you're safe to remove the lines of code. Just keep a back up of the original code just in case!
Add comment