84ea77ead6
* remove BOOTMAGIC_ENABLE=lite setting * change keyboard BOOTMAGIC_ENABLE rules Edits keyboard-level instances of `BOOTMAGIC_ENABLE = lite` to `BOOTMAGIC_ENABLE = yes`. * change keyboard BOOTMAGIC_ENABLE inline comments Edits keyboard-level BOOTMAGIC_ENABLE inline comments to "Enable Bootmagic Lite". * change keymap BOOTMAGIC_ENABLE rules Edits keymap-level instances of `BOOTMAGIC_ENABLE = lite` to `BOOTMAGIC_ENABLE = yes`. * change keymap BOOTMAGIC_ENABLE inline comments Edits/adds keymap-level BOOTMAGIC_ENABLE inline comments to read "Enable Bootmagic Lite". * change layout/user BOOTMAGIC_ENABLE rules/comments Edits instances of `BOOTMAGIC_ENABLE = lite` to `BOOTMAGIC_ENABLE = yes`. Edits/adds keymap-level BOOTMAGIC_ENABLE inline comments to read "Enable Bootmagic Lite". * update non-rules.mk BOOTMAGIC_ENABLE references in keyboards/ * remove docs references to Full Bootmagic * convert data-driven Bootmagic Lite instances * remove Bootmagic Lite bodge from data-driven generation * Merge remote-tracking branch 'upstream/develop' into rm/bootmagic-full_q4a * update docs/ja/config_options.md per mtei * update docs/faq_misc.md per mtei Remove remaining Full Bootmagic reference. |
||
|---|---|---|
| .. | ||
| keymaps | ||
| config.h | ||
| halconf.h | ||
| info.json | ||
| matrix.c | ||
| mcuconf.h | ||
| moonlander.c | ||
| moonlander.h | ||
| readme.md | ||
| rules.mk | ||
Moonlander
A next-gen split, ergonomic keyboard with an active left side, USB type C, integrated wrist rest, and a thumb cluster that can move.
- Keyboard Maintainer: drashna, ZSA
- Hardware Supported: Moonlander MK 1 (STM32F303xC)
- Hardware Availability: ZSA Store
Make example for this keyboard (after setting up your build environment):
make moonlander:default
Flashing example for this keyboard:
make moonlander:default:flash
See the build environment setup and the make instructions for more information. Brand new to QMK? Start with our Complete Newbs Guide.
Moonlander Customization
Indicator LEDs
There are 6 functions for enabling and disabling the LEDs on the top of the boards. The functions are ML_LED_1(bool) through ML_LED_6(bool), with the first LED being the left most LED on the left hand, and the sixth LED being the right most LED on the right side.
By default, the Indicator LEDs are used to indicate the layer state for the keyboard. If you wish to change this (and indicate caps/num/scroll lock status instead), then define MOONLANDER_USER_LEDS in your config.h file.
Oryx Configuration
To enable the features from Oryx (ZSA's Configurator), either compile the the default keymap, or add #define ORYX_CONFIGURATOR to your config.h file.
This enables the front Indicator LEDs, and the TOGGLE_LAYER_COLOR keycode. The TOGGLE_LAYER_COLOR keycode toggles the customized LED map configured on Oryx.
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.