[Keymap] Add andrebrait layout for GMMK Pro

[andrebrait]

Description

Just my own layout with an implementation for the CAPS LOCK indicator that works regardless of the actual status of the RGB Matrix.

Types of Changes

• Core
• Bugfix
• New feature
• Enhancement/optimization
• Keyboard (addition or update)
• Keymap/layout/userspace (addition or update)
• Documentation

Issues Fixed or Closed by This PR

Checklist

• My code follows the code style of this project: C, Python
• I have read the PR Checklist document and have made the appropriate changes.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• I have tested the changes and verified that they work and don't break anything (as well as I can manage).

[stickandgum]

Hi @andrebrait, I'm new to QMK and the GMMK Pro and trying my own custom keymap.c. Learning from what you've done here. (My messy keymap is not quite right : https://paste.ofcode.org/4vYCedvzfpKBcN4qKBuSb4 )

Can you tell me what each line does in the following snippet (I understand IFDEF checks to make sure RGB_MATRIX_ENABLE is yes in rules.mk:

#ifdef RGB_MATRIX_ENABLE
void keyboard_post_init_user(void) {
    /*
    Custom handling of RGB_TOG means it is impossible to toggle the RGB Matrix on and off and we
    need it to be enabled for the CAPS LOCK indicator to work, so enable it and then make sure it
    gets persisted to the EEPROM.
     */
    if (!rgb_matrix_is_enabled()) {
        rgb_matrix_enable_noeeprom();
        eeconfig_update_rgb_matrix();
    }
}

If the RGB is NOT enabled you have :
rgb_matrix_enable_noeeprom();
eeconfig_update_rgb_matrix();

Aren't these two functions the same as: rgb_matrix_enable() alone?

[andrebrait]

@drashna without this the GMMK Pro wouldn't wake up from a USB suspend. I guess this now counts as a bugfix 😛

[andrebrait]

With it, it's somewhat random whether or not it will wake, but I won't spend too much time on this. I can revert this bit if you think it's better to leave this out.

[andrebrait]

My bad for the apparent mess and number of commits. I was refining the logic yesterday and I just finished it.

Now I don't control writes to the EEPROM manually. Using flags to control state is quite clean, in the end.
I implemented a blinking indicator when toggling NKRO. Since it's just a little of RGB stuff, I did it on the keymap itself.

[andrebrait]

@stickandgum 5ms because I had a couple double leys with 2ms and with the new debouncing algorithm I figured I would have low latency even when pressing keys like crazy, but I have a proposal for making debounce changeable during execution that hasn't received comments yet.

As for waking up, currently any key works for me. I guess it's more of a computer firmware thing than an OS thing (though I think you can use the OS to configure that on the computer's firmware level).

[drashna]

Thanks!