qmk_firmware/keyboards/orthodox/keymaps/drashna
Konstantin Đorđević 4d9b11af14 Fix Command feature: use get_mods() instead of keyboard_report->mods (#4955)
* Remove unnecessary IS_COMMAND definition in clueboard/66/rev4

* Replace keyboard_report->mods with get_mods() in IS_COMMAND definitions

* Update docs to use get_mods() instead of keyboard_report->mods

* Replace keyboard_report->mods with get_mods() in tmk_core/protocol/usb_hid/test

For some reason, this occurrence used KB_LSHIFT and KB_RSHIFT, which don't exist

* Replace keyboard_report->mods with get_mods() in Massdrop keyboards (as per @patrickmt)
2019-01-27 00:28:40 -08:00
..
config.h Fix Command feature: use get_mods() instead of keyboard_report->mods (#4955) 2019-01-27 00:28:40 -08:00
keymap.c Keymap: Update for Drashna code - Proton C Prep Edition (#4708) 2018-12-31 14:29:56 -08:00
README.md
rules.mk Update to drashna keymaps and userspace - RGB edition (#4143) 2018-10-15 15:34:49 -04:00

Overview

This is my personal Orthodox configuration, and my daily driver.

Most of the code resides in my userspace, rather than here, as I have multiple keyboards.

How to build

make orthodox/rev1:drashna:teensy

Layers

  • QWERTY/DVORAK/COLEMAK/WORKMAN: basic layout, default set like the OLKB boards. Default is set and persists on power cycle.
  • RAISE: Contains function keys and unshifted symbols
  • LOWER: Contains function keys and shifted symbols
  • ADJUST: contains special codes (layout defaults, RGB codes, Audio codes, and volume control)

All layers have RGB specific indicators, so you can see what layer you're on by the underglow.

Orthodox Specific Code

Shift, Control and Alt all light up a specific RGB LED for a certain color, based on it's status, adding a visual indicator of OSMs or regular mods are held down.