drashna/qmk_firmware
1
0
Fork 0
Code Activity Actions

[Keymap Removal] keebio/iris and related keymaps. (#22690)

Browse source
This commit is contained in:
Joel Challis 2023-12-18 01:49:19 +00:00 • committed by GitHub
parent 54200b7b82
commit 990895f03f
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
230 changed files with 0 additions and 12906 deletions
Download patch file Download diff file Expand all files Collapse all files

28
keyboards/wilba_tech/rama_works_m6_a/keymaps/krusli/README.md
View file

@ -1,28 +0,0 @@
# krusli's RAMA M6-A Layout
Personal keymap for the RAMA M6-A.
Keymap was from my own port for the M6-A before official support was added, thus the backlighting code is not ported yet from the official default keymap.
Top-right button acts as a "toggle between layers" button. Layer 0 -> Layer 1 -> Layer 2 -> Layer 0 -> ...
* Layer 0: Git and Discord shortcuts
* Layer 1: Media playback and volume controls
* Layer 2: Osu! gamepad layer
## Helpful alternative keymaps (WIP)
### Arrow cluster
Use [karabiner-elements](https://github.com/tekezo/Karabiner-Elements) on macOS so that the state of the modifiers (shift, caps lock) are synchronised between keyboards (for shift + arrow key text selection, for example). It's also a handy tool for customising keyboard behaviour on a Mac.
On Windows/Linux modifier state should be shared between all keyboards by default.
Installation: install [homebrew](https://brew.sh) and run `brew install Caskroom/cask/karabiner-elements`.
```C
LAYOUT(
KC_ESC, KC_UP, TO(_LAYER0),
KC_LEFT, KC_DOWN, KC_RIGHT
)
```

71
keyboards/wilba_tech/rama_works_m6_a/keymaps/krusli/keymap.c
View file

@ -1,71 +0,0 @@
#include QMK_KEYBOARD_H
#include "action_layer.h"
#include "eeconfig.h"
extern keymap_config_t keymap_config;
// Each layer gets a name for readability, which is then used in the keymap matrix below.
// The underscores don't mean anything - you can have a layer called STUFF or any other name.
// Layer names don't all need to be of the same length, obviously, and you can also skip them
// entirely and just use numbers.
enum layers
{
_LAYER0,
_LAYER1,
_LAYER2
};
enum custom_keycodes
{
GIT_ADD = SAFE_RANGE,
GIT_COMMIT,
GIT_PUSH,
MUTE,
DEAFEN
};
bool process_record_user(uint16_t keycode, keyrecord_t *record)
{
if (record->event.pressed)
{
switch (keycode)
{
case GIT_ADD:
SEND_STRING("git add ." SS_TAP(X_ENTER));
break;
case GIT_COMMIT:
SEND_STRING("git commit -m " SS_DOWN(X_LSFT) SS_TAP(X_QUOTE) SS_UP(X_LSFT));
break;
case GIT_PUSH:
SEND_STRING("git push" SS_TAP(X_ENTER));
break;
case MUTE:
SEND_STRING(SS_LGUI(SS_LSFT("M")));
break;
case DEAFEN:
SEND_STRING(SS_LGUI(SS_LSFT("D")));
break;
return false;
}
}
return true;
};
const uint16_t PROGMEM keymaps[][MATRIX_ROWS][MATRIX_COLS] = {
[_LAYER0] = LAYOUT(
MUTE, DEAFEN, TO(_LAYER1),
GIT_ADD, GIT_COMMIT, GIT_PUSH),
[_LAYER1] = LAYOUT(
KC_VOLD, KC_VOLU, TO(_LAYER2),
KC_MRWD, KC_MPLY, KC_MNXT),
[_LAYER2] = LAYOUT(
KC_ESC, KC_UP, TO(_LAYER0),
KC_Z, KC_X, KC_SPACE)};
void matrix_init_user(void)
{
#ifdef BACKLIGHT_ENABLE
backlight_level(0);
#endif
}