-
-
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
Allow mod-tap hold action on one shot layer #19214
Conversation
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.
Also, could you add to the unit tests to ensure that this behavior is properly tested?
I added a few unit tests and fixed a small bug that I discovered thanks to the tests. I'm not sure that's enough. It certainly doesn't test all permutations of all Tap-Hold options. |
Well, having them at all is a huge thing. And they've already proven when even basic tests are definitely better than nothing, here. :) At the very least, it helps with confidence in the code. And more robust testing can be added later. |
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.
Thanks for fixing bugs and adding unit-tests in the progress! This is much appreciated. The changes LGTM.
Description
This proposal allows mod-tap hold action on one shot layer. One shot layer is immediately disabled if
MT()
is pressed and therefore mod-tap hold is not possible.Example:
Following example currently produce a lower case character
x
.OSL(L2)
downOSL(L2)
upLSFT_T(...)
downKC_A
downKC_A
upLSFT_T(...)
upWith the proposed change the result is a upper case
A
and it will behave same asKC_LSFT
.I'm not aware if this covers all possible situations, but I've tested it for several months with no problems.
Types of Changes
Checklist