Skip to content
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

Timeout should measure from last activation rather than first activation. #3

Open
amacleod opened this issue Nov 3, 2024 · 1 comment

Comments

@amacleod
Copy link

amacleod commented Nov 3, 2024

After setting timeout-ms to 1500, I have observed that the third behavior gets activated 1.5 seconds after the first behavior, regardless of how many times I activate the middle behavior.

The way I want it to work, which I think is consistent with the description in the readme, is for it to activate the third behavior 1500 milliseconds after the last time I touch the key (or keep the timer alive by touching an ignored key).

Setting timeout-ms will cause the deactivation behavior to fire when the time has elapsed after releasing the Tri-State or a ignored key.

@amacleod
Copy link
Author

amacleod commented Nov 3, 2024

Practically speaking, I probably do not need timeout-ms, and can instead rely on the interrupt functionality. The only downside I can imagine is for my alt-tab tri-state to just leave alt pressed for a long time until I decide to press something else.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant