TAPDANCE outside Xorg

[andmarti1424]

Hello. I have a planck with qmk. I have a tapdance on tab key to act as a left control when held. And as a tab on single press. TAPDANCE is working fine on my Xorg session, but it does not work on sway (wayland) nor outside X.. Is this expected? Any workaround this? Thanks!

[lesshonor]

While the proposed solution is not easily usable at present due to code conflicts, see #19449 for more information/discussion about this problem.

Note that if you are using GNOME, this issue may be resolved in a later release.

[andmarti1424]

While the proposed solution is not easily usable at present due to code conflicts, see #19449 for more information/discussion about this problem.

Note that if you are using GNOME, this issue may be resolved in a later release.

But where is the problem? I don't use shift modifier. Just a tab when single pressed or ctrl modifier when held.

[lesshonor]

From the description of the pull request:

QMK has trouble sending modifier keys [...]

Control is also a modifier...

Anyway, there is a lot of information in that pull request including links to related issues and alternative solutions, but if you aren't interested in reading any of it you can just try setting #define TAP_CODE_DELAY to a small value (like 10) in your keymap's config.h as a workaround.

[andmarti1424]

@lesshonor thank you. Im afraid that didnt change a thing. I had to redefine it cause it was already defined to 0 value. Im using sway by the way. but as I said earlier, this happens also outside wayland. Will try to #define DOUBLE_REPORT but since it was a PR that was not merged.. I expect it behave the same way.

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had activity in the last 90 days. It will be closed in the next 30 days unless it is tagged properly or other activity occurs. For maintainers: Please label with bug, in progress, on hold, discussion or to do to prevent the issue from being re-flagged.

[github-actions[bot]]

This issue has been automatically closed because it has not had activity in the last 30 days. If this issue is still valid, re-open the issue and let us know. // [stale-action-closed]