Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Fixes a couple of issues with
combo_disablefunction calls.The key buffer was not emptied when disabling combos; I had removed the
dump_key_buffer()call as it could lead to infinite loops. Removing the call it seems wasn't the right move.Now recursive calls to
dump_key_bufferstart from the next key instead of the key that is "currently being dumped" from the buffer.Another issues with disabling combos was that any currently active combo wasn't released on key releases.
Now combo key releases are always handled, even if combo processing is disabled.
Easy way to test the current issues:
LT(_LAYER, KC_X)_LAYER, calldisable_combo()Then just hold the combo for a while to activate the layer. On release the layer stays on.
I've messaged the two I know had issues with this to review this.
Types of Changes
Checklist