4b453dca92
* remove keyboard-level instances of `MIDI_ENABLE = no`
Command:
```
find keyboards/ -type f -name 'rules.mk' -and -not -path '*/keymaps/*' -exec sed -i -e '/^[ #]*MIDI_ENABLE[ \t]*=[ \t]*no/d' {} +
```
Co-Authored-By: Nick Brassel <nick@tzarc.org>
* fix case-sensitivity issues on MIDI_ENABLE
Change instances of `MIDI_ENABLE = YES` to `MIDI_ENABLE = yes`.
Command:
```
find keyboards/ -type f -name 'rules.mk' -and -not -path '*/keymaps/*' -exec sed -i -e 's;MIDI_ENABLE[ \t]*=[ \t]*[Yy][Ee][Ss];MIDI_ENABLE = yes;g' {} +
```
* replace `# MIDI controls` with `# MIDI support`
Replace `# MIDI controls` with `# MIDI support` in keyboard-level `rules.mk` files.
Command:
```
find keyboards/ -type f -name 'rules.mk' -and -not -path '*/keymaps/*' -exec sed -i -e 's;#[ \t]*MIDI[ \t]*\(controls\|support\).*;# MIDI support;g' {} +
```
* align inline comments
Aligns the inline comments to the length used by the QMK AVR rules.mk template.
Command:
```
find keyboards/ -type f -name 'rules.mk' -and -not -path '*/keymaps/*' -exec sed -i -e 's;MIDI_ENABLE *= *yes.*;MIDI_ENABLE = yes # MIDI support;g' {} +
```
* remove commented instances of `MIDI_ENABLE` from keyboard `rules.mk` files
Commands:
```
find keyboards/ -type f -name 'rules.mk' -and -not -path '*/keymaps/*' -exec sed -i -e 's;#\([ \t]*MIDI_ENABLE\) = yes; \1 = no ;' {} +
find keyboards/ -type f -name 'rules.mk' -and -not -path '*/keymaps/*' -exec sed -i -e 's;^\([ \t]*\)\(MIDI_ENABLE = no\);\2\1;' {} +
find keyboards/ -type f -name 'rules.mk' -and -not -path '*/keymaps/*' -exec sed -i -e '/^[ #]\+MIDI_ENABLE *= *no/d' {} +
```
* remove MIDI configuration boilerplate from keyboard config.h files
Co-authored-by: Nick Brassel <nick@tzarc.org>
|
||
|---|---|---|
| .. | ||
| glow | ||
| config.h | ||
| ez.c | ||
| ez.h | ||
| info.json | ||
| readme.md | ||
| rules.mk | ||
Planck EZ
A variant of the Planck featuring a 2u spacebar and per-key RGB backlighting.
Keyboard Maintainer: Jack Humbert, Drashna Jael're
Hardware Supported: Planck EZ
Hardware Availability: ZSA
Make example for this keyboard (after setting up your build environment):
make planck/ez:oryx
For the per key RGB version of this keyboard, you want to use the "glow" subdirectory. For example:
make planck/ez/glow:oryx
See the build environment setup and the make instructions for more information. Brand new to QMK? Start with our Complete Newbs Guide.
Planck EZ Configuration (from Oryx)
To enable the features from Oryx (ZSA's Configurator), either compile the the oryx keymap, or add #define ORYX_CONFIGURATOR to your config.h file.
This enables the front Indicator LEDs, and the TOGGLE_LAYER_COLOR, and LED_LEVEL keycodes. The TOGGLE_LAYER_COLOR keycode toggles the customized LED map configured on Oryx. The LED_LEVEL cycles through the brightness levels for the front "teeth" LEDs.
Indicator LEDs
The two front "teeth" LED indicators are PWM controlled. If you have ORYX_CONFIGURATOR defined in your keymap's config.h, you can use the LED_LEVEL to cycle through preset vales (0, 25%, 50%, 75%, 100%), and will be saved to EEPROM (persistent storage)
Alternatively, you can set the brightness by calling the following functions:
void planck_ez_right_led_level(uint8_t level);
void planck_ez_left_led_level(uint8_t level);
These settings are not persistent, so you'd need to reset it every time the board starts.
These are on a 0-255 scale
Layer indication
By default, the indicator lights are used for layer indication, expecting the specific layers used in the default keymap. However, this may not work for you. And if that is the case, you can add #define PLANCK_EZ_USER_LEDS to your config.h file.
This will remove the default behavior for changing the LEDs based on layer, and allow you to control them manually.
Alternatively, you can use the following defines in your keymap's config.h to control which layers are used, as long as you have ORYX_CONFIGURATOR defined in your keymap's config.h file, as well.
#define PLANCK_EZ_LED_LOWER 3
#define PLANCK_EZ_LED_RAISE 4
#define PLANCK_EZ_LED_ADJUST 6
This will allow you to change the layers that are used, without having to add anything code to your keymap.c
RGB Matrix Features
If you're using the Smart LED (layer indication) feature from the Oryx Configurator, you want to make sure that you enable these options by adding #define ORYX_CONFIGURATOR to your keymap's config.h.
This changes the RGB_TOG keycode so that it will toggle the lights on and off, in a way that will allow the Smart LEDs to continue to work, even with the rest of the LEDs turned off.
Additionally, a new keycode has been added to toggle the Smart LEDs. Use TOGGLE_LAYER_COLOR, if you aren't already.