[Keymap] Fix my userspace RGB bug (#5686)
* fix bug that enabled RGBLIGHT_ENABLE on all my boards regardless if it was supported or not * update changelog with new changes for 0.2.2
|7 months ago|
|changelog.md||7 months ago|
|config.h||7 months ago|
|mechmerlin.c||1 year ago|
|mechmerlin.h||1 year ago|
|readme.md||9 months ago|
|rules.mk||9 months ago|
This is a collection of my most commonly used QMK features.
A majority of my keyboards are smaller than 75%, ANSI, and staggered.
Typical standard QWERTY keymap.
This layer is commonly accessed via
MO(_FL) on the base layer. It consists of your typical function key F1 through F12 and some RGB and Backlight controls.
This layer is only present on my 60% boards. I habitually use the bottom right modifiers as arrows.
This is not defined in here as it’s present only on
LAYOUT_66 boards, or to be specific, my clueboard. It currently uses the default clueboard controls.
KC_FNX functions as a hold for
MO(X) and tap for
TG(Y). Layer X and Y are different layers.
It is used primarily on my
LAYOUT_60_ansi boards as my regular toggle (the 1u key to the right of right shift), is not present there.
This is just a wrapper for
CTL_T(KC_CAPS). This is a hold for control and tap for caps lock.
Ensures that when my computer is in sleep mode, the keyboard underglow lights will also be off.
If a board has a speaker, enable beeps and boops per switch actuation. This is currently only available on prototype/gen1 clueboard 66_hotswaps.
Velocikey is an RGBLIGHT feature in which the faster you type, the faster the ARE GEE BEES.