Stack doesn't retain focus when doing cyclestack next #285

New Issue

2026-01-05T14:49:29+01:00

adam commented

2026-01-05 14:49:29 +01:00

Originally created by @jpmiller25 on GitHub (Jan 22, 2024).

I have an ahk hotkey mapped to CycleStack("next") which performs:

CycleStack(cycle_direction) {
RunWait("komorebic.exe cycle-stack " cycle_direction, , "Hide")
}
(from komorebic.lib.ahk)

I want to use it to quickly flip through the stack with one key. It keeps focus when I cycle through, but I think when it cycles back to the start is when focus switches to another window on a different screen. I am on a multiple monitor setup.

To Reproduce
Steps to reproduce the behavior:

ahk config - include komorebic.lib.ahk
map key to CycleStack("next")
Open any window on left screen
Open two windows on right screen stack them.
Use cycle hotkey to switch between windows in stack in repetition, after the first switch focus will switch over to window on left screen and then hotkey no longer does anything.

Expected behavior
Focus will remain on the window stack that is being cycled.

Originally created by @jpmiller25 on GitHub (Jan 22, 2024). I have an ahk hotkey mapped to CycleStack("next") which performs: CycleStack(cycle_direction) { RunWait("komorebic.exe cycle-stack " cycle_direction, , "Hide") } (from komorebic.lib.ahk) I want to use it to quickly flip through the stack with one key. It keeps focus when I cycle through, but I think when it cycles back to the start is when focus switches to another window on a different screen. I am on a multiple monitor setup. **To Reproduce** Steps to reproduce the behavior: 1. ahk config - include komorebic.lib.ahk 2. map key to CycleStack("next") 3. Open any window on left screen 4. Open two windows on right screen stack them. 5. Use cycle hotkey to switch between windows in stack in repetition, after the first switch focus will switch over to window on left screen and then hotkey no longer does anything. **Expected behavior** Focus will remain on the window stack that is being cycled.

adam added the bug label 2026-01-05 14:49:29 +01:00

adam closed this issue

2026-01-05 14:49:30 +01:00

adam commented

2026-01-05 14:49:30 +01:00

@LGUG2Z commented on GitHub (Feb 8, 2024):

Unfortunately I'm not able to reproduce this with the latest build from master and I don't remember coming across a similar issue before in earlier versions (I use the same stacking and cycling workflow quite a lot)

Can you try reproducing this with a build from master? If not, the next release should be out within the next two weeks to try to repro this again with an update from scoop or winget.

@LGUG2Z commented on GitHub (Feb 8, 2024): Unfortunately I'm not able to reproduce this with the latest build from `master` and I don't remember coming across a similar issue before in earlier versions (I use the same stacking and cycling workflow quite a lot) Can you try reproducing this with a build from `master`? If not, the next release should be out within the next two weeks to try to repro this again with an update from scoop or winget.

adam commented

2026-01-05 14:49:30 +01:00

@jpmiller25 commented on GitHub (Feb 15, 2024):

Thanks, building from source has corrected this issue.

@jpmiller25 commented on GitHub (Feb 15, 2024): Thanks, building from source has corrected this issue.

adam commented

2026-01-05 14:49:30 +01:00

@jpmiller25 commented on GitHub (Feb 15, 2024):

Closing

@jpmiller25 commented on GitHub (Feb 15, 2024): Closing

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/komorebi#285