|
|
1 year ago | |
|---|---|---|
| .. | ||
| keymap.json | 1a54ecf246 [Keyboard] Add splitkb.com's Halcyon Corne rev2 (#25143) | 1 year ago |
| readme.md | 1a54ecf246 [Keyboard] Add splitkb.com's Halcyon Corne rev2 (#25143) | 1 year ago |
_This keymap is a copy of the Corne default keymap_
Keymaps in general are quite personal, so it is difficult to come up with a default that will suit every user. We hope this keymap serves as a good starting point for your own - although it should be fairly usable out-of-the-box.
This is where your basic letters live.
The homing thumb fingers are used to access the different layers.
The Lower layer gives access to your number keys on the top row. It also exposes the arrow keys in the usual Vim-style layout.
The Raise layer gives access to the symbols. In addition to shifted number keys on the top row, the right hand also exposes the remaining symbol keys, both as shifted and non-shifted variants.
The Adjust layer exposes RGB adjustment keys on the left hand.
The keymap.c file is not published to the repository. It is generated from keymap.json by the build system.
This avoids duplicating information and allow users to edit their keymap from the QMK Configurator web interface.
The keymap.json file is generated from the QMK Configurator interface and formatted for better readability in the context of the Ferris keyboard.
To edit it, you may:
If you decide to use the latter workflow, here are the steps to follow:
<your qmk repo>/keyboards/splitkb/halcyon/corne/keymaps/default/keymap.json)While the json format is easy to use, it does lack certain functionality - most notably custom OLED or encoder behaviour.
To add this, you need to convert it to the c format. Do keep in mind that this is generally a one-way operation.
First, from the root of your qmk repo, move to your keymap folder
cd ./keyboards/splitkb/halcyon/corne/keymaps/my_personal_keymap
Next, convert your keymap.json to a keymap.c
qmk json2c -o keymap.c keymap.json
You can add custom C code to the newly generated keymap.c file. Do note that you have to use either a C file or a JSON file - you cannot do both!
If a JSON file is present, the C file is ignored.



