gmmk/pro/mike1808 keymap

[mike1808]

Description

Add my keymap for gmmk/pro

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

None

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

[ach5948]

The RGB Matrix LEDMap is a really cool idea!

[cj360]

The Ledmap is awesome though I'm at a loss as to why its setting the rgb to white on function layer when I attempt to copy it.

[mike1808]

hey @cj360 can you tell me your content of rules.mk?

[cj360]

Sure thing here's a gist.

[mike1808]

@cj360 looks fine. I'm curious, why it can set rgb to white. I don't have any code setting it to white. Can you try to run qmk clean before compiling it? Also, maybe you have conflicting RGB code in rgb_matrix_indicators_advanced_user

[ForsakenRei]

The LED matrix is really a cool idea, which will make customized LEDs for layers way easier.
If I want to use it with my existing keymap.c, except the LED layout I need to copy to my keymap.c and the rules.mk I need change, which files will be essential to have the LED layout functionable?

[mike1808]

@ForsakenRei that was my initial implementation, but it was consuming a lot of memory. The current implementation requires you to define a macro mapping each key to RGB index in g_led_config.

[ForsakenRei]

@ForsakenRei that was my initial implementation, but it was consuming a lot of memory. The current implementation requires you to define a macro mapping each key to RGB index in g_led_config.

I see. Thanks for the tip, I will give it a try.