-
-
Notifications
You must be signed in to change notification settings - Fork 40.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update adamtabrams keymap #21344
Update adamtabrams keymap #21344
Conversation
* handle mod tap for keys on the same side * update config values * remove some tapping force hold * update keymap and config
CI build failures showing |
https://github.com/qmk/qmk_firmware/pull/21344/checks?check_run_id=14573543723
Seems a bit strange that I would need to include a library I have no use for to make my keymap compatible with a hardware revision I'm not using. |
You can move your keymap under your particular revision folder; it will then only be built for that rev. |
I noticed that |
If rev7 relies on the |
I'm in agreement that the build failure for rev7 should be resolved at keyboard level, not keymap level. |
#21408 should fix the failure for |
bool is_left_key(int row) { | ||
return row < 4 || row == 7; | ||
} | ||
|
||
bool is_right_key(int row) { | ||
return row > 2; | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This part is actually specific to planck rev6 (and rev7, which apparently has the same matrix). And technically the handling of rows 3 and 7 is wrong (row 3 is used for both far left and far right keys on the bottom row, and row 7 is used by the central 6 keys of the bottom row).
clear_mods(); | ||
for (int i = 0; i < num_mods; i++) { | ||
if (counts[i] == 0) { | ||
tap_code16(mods[i]); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This effectively does
tap_code16(mods[i]); | |
tap_code(QK_MOD_TAP_GET_TAP_KEYCODE(mods[i])); |
However, that peculiarity of the tap_code16()
behavior (keycodes outside of the QK_BASIC
…QK_MODS_MAX
range are truncated to the low byte) does not seem to be documented anywhere.
Thank you for your contribution! |
Thank you for your contribution! |
It wont be merged #22724.
|
@zvecr Thanks for the quick response. And I'm glad to hear this! |
Description
Types of Changes
Issues Fixed or Closed by This PR
Checklist