mirror of
https://github.com/Keychron/qmk_firmware.git
synced 2024-11-26 10:27:52 +06:00
Move ALT...
This commit is contained in:
parent
0db06def9b
commit
24e8d01dc9
|
@ -92,6 +92,7 @@ enum macro_id {
|
|||
#define RANDALP M(M_RANDLETTER)
|
||||
#define CTLENTER MT(MOD_RCTL, KC_ENT)
|
||||
#define SHIFTQUOTE MT(MOD_RSFT, KC_QUOT)
|
||||
#define ALTRIGHT MT(MOD_LALT, KC_RGHT)
|
||||
|
||||
|
||||
/* Note that Planck has dimensions 4 rows x 12 columns */
|
||||
|
@ -101,7 +102,7 @@ const uint16_t PROGMEM keymaps[][MATRIX_ROWS][MATRIX_COLS] = {
|
|||
{KC_ESC, KC_Q, KC_W, KC_E, KC_R, KC_T, KC_Y, KC_U, KC_I, KC_O, KC_P, KC_BSPC},
|
||||
{KC_LCTL, KC_A, KC_S, KC_D, KC_F, KC_G, KC_H, KC_J, KC_K, KC_L, KC_SCLN, CTLENTER},
|
||||
{KC_LSFT, KC_Z, KC_X, KC_C, KC_V, KC_B, KC_N, KC_M, KC_COMM, KC_DOT, KC_SLSH, SHIFTQUOTE },
|
||||
{KC_TAB, ROT_LED, KC_LALT, KC_LGUI, M_LOWER, KC_SPC, KC_SPC, M_UPPER, KC_LEFT, KC_DOWN, KC_UP, KC_RGHT}
|
||||
{KC_TAB, KC_LALT, ROT_LED, KC_LGUI, M_LOWER, KC_SPC, KC_SPC, M_UPPER, KC_LEFT, KC_DOWN, KC_UP, ALTRIGHT}
|
||||
/* Note that KC_SPC is recorded TWICE, so that either matrix position can activate it */
|
||||
},
|
||||
[_RAISE] = { /* RAISE */
|
||||
|
|
|
@ -27,10 +27,23 @@ doing sundry experimentation:
|
|||
* Trying out sgoodwin's "hold Enter down to get Shift"
|
||||
- Liking this Quite Well Enough...
|
||||
- Applied this to both Shift and Quote
|
||||
- It seems likely that Alt should get a right-hand-side, akin to this...
|
||||
- Alt needs to move, and get a RHS
|
||||
- Hence ALTRIGHT, and shifted ROT_LED over
|
||||
- Emacs likes this!!! :-)
|
||||
- I'm suspicious that I'll want to shift ROT_LED another location over,
|
||||
so some modifier can replace the OS/KC_LGUI key
|
||||
* I have added an alternate ADJUST layer that is activated via update_tri_layer()
|
||||
- e.g. - LOWER+RAISE simultaneously
|
||||
- This seems entirely more useful for handling my "special keys"
|
||||
like the random numbers, user name, and such, than the keypad layer
|
||||
* The _ADJUST layer provides a good place to have RESET
|
||||
- But this isn't strictly enough; I want RESET somewhat accessible from
|
||||
main layer lest an error hide that layer
|
||||
- I never use the OS/KC_LGUI key (that's Command on MacOS, Windows
|
||||
Key on Windows), so that's a good place to have it as a chord of
|
||||
some sort
|
||||
|
||||
|
||||
2. Some code structure ideas
|
||||
---------------------------------------------------
|
||||
|
@ -49,8 +62,8 @@ doing sundry experimentation:
|
|||
only need to fit 4 symbols onto each line, rather than 12.
|
||||
|
||||
I used enums to manage layer IDs and macro IDs so that I don't need
|
||||
to care (beyond "start at 0", and arguably that's not needed) about
|
||||
their values.
|
||||
to care (beyond "start at 0", and arguably even that's not needed)
|
||||
about their values.
|
||||
|
||||
3. Things I did not like about the default mapping
|
||||
---------------------------------------------------------
|
||||
|
@ -83,8 +96,6 @@ unwise things again...
|
|||
to allow selecting multiple items, and this really interferes
|
||||
with that
|
||||
|
||||
|
||||
|
||||
5. TODO
|
||||
---------------------------------------------------------
|
||||
|
||||
|
|
Loading…
Reference in New Issue
Block a user