You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using TabStack 1.2.1, did not try earlier versions. Windows 10 and 11.
Sometimes, when I press Ctrl+Tab fast, just nothing happens. I.e. no tabs switching.
If I disable TabStack, fast Ctrl+Tab always switches tabs.
I assume it has something to do with the timeouts inside of TabStack's code. Could you suggest what exact values I may try to improve the behavior?
Update:
Just observed a strange behavior: after Ctrl+Tab has been pressed with TabStack's popup shown (Ctrl is held), each Tab press goes to the previous item as if Shift is held, but Shift is not actually held. Arrow Down and Arrow Up work as expected. Probably it's something related to synchronization issues? E.g. some state has been preserved or incorrectly changed?
AI suggests to change the line 73 in "session.py":
if state.ctrl_release_poller is not None and not state.ctrl_release_poller.is_ctrl_down():
state.clear_session()
return
to the following:
if state.ctrl_release_poller is not None and not state.ctrl_release_poller.is_ctrl_down():
# A fast tap releases Ctrl before this deadline. Committing here
# covers the case where the poller's callback has not run yet;
# clearing instead drops the tab switch.
_commit_pending_session(window, state)
return
This seems to fix the quick Ctrl+Tab at least. (I'm still trying to understand how to reproduce the opposite direction Ctrl+Tab behavior. Maybe it was the consequence of the fast Ctrl+Tab issue?)
Activity
d0vgan commentedon Oct 4, 2026
AI suggests to change the line 73 in "session.py":
to the following:
This seems to fix the quick Ctrl+Tab at least. (I'm still trying to understand how to reproduce the opposite direction Ctrl+Tab behavior. Maybe it was the consequence of the fast Ctrl+Tab issue?)
FichteFoll commentedon Oct 14, 2026
Thanks for the report. I accidentally fixed this in #12 via 91f7289 already.