drashna/qmk_firmware
1
0
Fork 0
Code Activity Actions

[Keyboard] Assorted personal keymap/layout updates (#6621)

Browse source 
* Switch Quefrency back to I2C (#6161 fixes the lag)

* Update Quefrency keymap

* Add reset and EEPROM reset keybindings so these tasks can be performed
separately, rather than relying on Bootmagic Lite, which performs both
tasks at the same time.

* Move Caps Lock from Fn+Ctrl to Fn+Tab since Fn+Ctrl is sometimes used
as part of a more complex keybinding, whereas Fn+Tab is always safe.

* Update KBD67 keymap

* Add reset and EEPROM reset keybindings so these tasks can be performed
separately, rather than relying on Bootmagic Lite, which performs both
tasks at the same time.

* Move Caps Lock from Fn+Ctrl to Fn+Tab since Fn+Ctrl is sometimes used
as part of a more complex keybinding, whereas Fn+Tab is always safe.

* Move Menu to a layer tap on the Fn key since that's a more natural
location.

* Update 60% Tsangan HHKB layout

* Move Caps Lock from Fn+Ctrl to Fn+Tab since Fn+Ctrl is sometimes used
as part of a more complex keybinding, whereas Fn+Tab is always safe.

* Update 60% ANSI split backspace/right-shift layout

* Add reset and EEPROM reset keybindings so these tasks can be performed
separately, rather than relying on Bootmagic Lite, which performs both
tasks at the same time.

* Move Caps Lock from Fn+Ctrl to Fn+Tab since Fn+Ctrl is sometimes used
as part of a more complex keybinding, whereas Fn+Tab is always safe.
This commit is contained in:
Jonathan Rascher 2019-08-30 19:45:49 -05:00 • committed by Drashna Jaelre
parent 733ec614d8
commit 9340b70b7e
9 changed files with 21 additions and 33 deletions
Download patch file Download diff file Expand all files Collapse all files

14
keyboards/keebio/quefrency/keymaps/bcat/config.h
View file

@ -1,18 +1,6 @@
#pragma once
/*
* I2C seems to randomly drop keystrokes. Not sure why. It seems a bit like
* https://github.com/qmk/qmk_firmware/issues/5037, but that issue is closed,
* and our problems happen even with underglow disabled.
*
* This issue occurs with multiple TRRS cables of different lengths from
* different companies, so it's most likely not a cable issue. It may be that
* we are running into issues with long I2C runs, in which case stronger
* pull-up resistors might help:
* https://hackaday.com/2017/02/08/taking-the-leap-off-board-an-introduction-to-i2c-over-long-wires/.
* For now, just don't use I2C.
*/
#define USE_SERIAL
#define USE_I2C
/* Use an extra LED on the right side since it's wider on the 65% PCB. */
#undef RGBLED_NUM

4
keyboards/keebio/quefrency/keymaps/bcat/keymap.c
View file

@ -21,8 +21,8 @@ const uint16_t PROGMEM keymaps[][MATRIX_ROWS][MATRIX_COLS] = {
/* Function layer: http://www.keyboard-layout-editor.com/#/gists/59636898946da51f91fb290f8e078b4d */
[LAYER_FUNCTION] = LAYOUT_65(
_______, KC_F1, KC_F2, KC_F3, KC_F4, KC_F5, KC_F6, KC_F7, KC_F8, KC_F9, KC_F10, KC_F11, KC_F12, KC_INS, KC_DEL, RGB_HUI,
_______, KC_MPLY, KC_VOLU, KC_MSTP, _______, _______, _______, _______, KC_PSCR, KC_SLCK, KC_PAUS, _______, _______, _______, RGB_SAI,
KC_CAPS, KC_MPRV, KC_VOLD, KC_MNXT, _______, _______, _______, _______, _______, _______, _______, _______, RGB_TOG, RGB_SAD,
KC_CAPS, KC_MPLY, KC_VOLU, KC_MSTP, _______, _______, EEP_RST, RESET, KC_PSCR, KC_SLCK, KC_PAUS, _______, _______, _______, RGB_SAI,
_______, KC_MPRV, KC_VOLD, KC_MNXT, _______, _______, _______, _______, _______, _______, _______, _______, RGB_TOG, RGB_SAD,
_______, _______, KC_MUTE, _______, _______, _______, _______, _______, _______, _______, _______, _______, RGB_VAI, RGB_HUD,
_______, _______, _______, _______, _______, _______, _______, _______, _______, _______, RGB_RMOD, RGB_VAD, RGB_MOD
),

2
keyboards/keebio/quefrency/keymaps/bcat/readme.md
View file

@ -10,4 +10,4 @@ cluster, and RGB controls in the function layer on the arrow/nav keys.
## Function layer
![Function layer layout](https://i.imgur.com/4R1F72M.png)
![Function layer layout](https://i.imgur.com/0mvzXHG.png)