qmk_firmware/keyboards/moonlander
Ryan 5974d989fe
Normalise Unicode keycodes (#18898)
* `UC_MOD`/`UC_RMOD` -> `UC_NEXT`/`UC_PREV`

* `UNICODE_MODE_*` -> `QK_UNICODE_MODE_*`

* `UC_MAC` -> `UNICODE_MODE_MACOS`

* `UC_LNX` -> `UNICODE_MODE_LINUX`

* `UC_WIN` -> `UNICODE_MODE_WINDOWS`

* `UC_BSD` -> `UNICODE_MODE_BSD`

* `UC_WINC` -> `UNICODE_MODE_WINCOMPOSE`

* `UC_EMACS` -> `UNICODE_MODE_EMACS`

* `UC__COUNT` -> `UNICODE_MODE_COUNT`

* `UC_M_MA` -> `UC_MAC`

* `UC_M_LN` -> `UC_LINX`

* `UC_M_WI` -> `UC_WIN`

* `UC_M_BS` -> `UC_BSD`

* `UC_M_WC` -> `UC_WINC`

* `UC_M_EM` -> `UC_EMAC`

* Docs

* Update quantum/unicode/unicode.h
2022-10-31 21:15:12 +00:00
..
keymaps Normalise Unicode keycodes (#18898) 2022-10-31 21:15:12 +00:00
config.h Change DRIVER_LED_COUNT to {LED,RGB}_MATRIX_LED_COUNT (#18399) 2022-09-23 22:46:23 +10:00
halconf.h [Keyboard] Move Moonlander off 'Proton C' board (#14478) 2021-09-17 13:00:42 -07:00
info.json Move keyboard USB IDs and strings to data driven: M (#17859) 2022-08-03 17:15:43 +10:00
matrix.c Expose Moonlander split detection to user code (#18040) 2022-08-29 02:37:29 +01:00
mcuconf.h [Keyboard] Move Moonlander off 'Proton C' board (#14478) 2021-09-17 13:00:42 -07:00
moonlander.c Remove some assumptions on sequential keycode ranges (#18838) 2022-10-24 22:07:34 -07:00
moonlander.h Mark the moonlander keyboard default music map as weak (#18715) 2022-10-16 03:31:51 +01:00
readme.md Expose Moonlander split detection to user code (#18040) 2022-08-29 02:37:29 +01:00
rules.mk [Keyboard] Update to ZSA Keyboards (#15644) 2021-12-29 06:14:48 -08:00

Moonlander

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

Detecting split / Gaming mode

To make it extra gaming friendly, you can configure what happens when you disconnect the right half. This is especially useful when using gaming unfriendly layers or layouts (e.g. home row mods, dvorak, colemak).

Example for enabling a specific layer while right side is disconnected:

void housekeeping_task_user(void) {
    if (!is_transport_connected()) {
        // set layer
    }
}