diff options
| author | James Young <18669334+noroadsleft@users.noreply.github.com> | 2021-10-13 05:47:54 +0000 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2021-10-12 22:47:54 -0700 |
| commit | bc51e330c0c183e78e415b6cfbf475990eb1ba86 (patch) | |
| tree | d287cd482104a3769259d4b70238a4e5114826a2 /keyboards/westfoxtrot/aanzee/aanzee.h | |
| parent | c63c78f0801f595f2200dab7246a1264b1ec847d (diff) | |
| download | qmk_firmware-bc51e330c0c183e78e415b6cfbf475990eb1ba86.tar.gz qmk_firmware-bc51e330c0c183e78e415b6cfbf475990eb1ba86.zip | |
Lucid Alexa layout macro rework (#14799)
* refactor keymaps for readability
- use QMK-native keycode aliases
- physically align keycodes
* rework layout macro
A discrepancy between the default and via keymaps prompted a deep dive into the keyboard's switch matrix, which led to the discovery that (1) the layout macro's arguments were not arranged physically, and (2) the keymaps didn't assign the keycodes to the same switches (the default keymap's keycodes were in the wrong sequence).
Additionally, the layout macro was built to support a split Backspace, but named as if it were for a 2u Backspace, which broke the enabled support for Community Layout keymaps.
This commit:
- arranges the layout macro arguments according to physical order
- corrects the keymaps
- renames the layout macro to specify the split Backspace
- disables Community Layout support
- updates the `info.json` data
* add LAYOUT_65_ansi_blocker
* enable Community Layout support
* update `info.json` metadata
- use full product listing URL
- use GitHub username for maintainer field
* update readme
- fix vendor link in lead paragraph
- update metadata list
- use GitHub username of keyboard maintainer
- correct Supported Hardware
- add Hardware Availability link
- add flashing and bootloader instructions
Diffstat (limited to 'keyboards/westfoxtrot/aanzee/aanzee.h')
0 files changed, 0 insertions, 0 deletions