🐞 Next Screen odd behavior in v1.4.0 1585

[Ender-Wang]

Bug Description

I have "resize window under cursor" off.

When cycling the current focus window through screens,

• If I put my pointer on the screen where the focus window is, then cycle through via keyboard shortcuts, the focus screen moves to the relative position on the next screen. etc., I positioned the screen to the left edge, and then it appears in the same position on the next screen, which is expected.
• If I put my pointer on the other screens (not on the screen where the focus window is), then cycle through the focus window, it moves to the next screen and is aligned to the left bottom edge of that screen, it's not positioned to the relative position of the original screen.

If I enable 'Resize window under cursor', it behaves as expected, moving to the relative position.

Steps To Reproduce

Expected Behavior

Actual Behavior

Screenshots

No response

macOS Version

15.7.2

Loop Version

v1.4.0 1585

Additional Context

No response

Final Checks

• My issue is written in English
• My issue title is descriptive
• This is a single bug (multiple bugs should be reported individually)
• I can help with fixing or developing this issue (tick if you can help).

[mrkai77]

Thanks for the report. Would you be able to send over your keybinds file, as well as console logs when this occurs? You can filter for Loop's logs by setting a filter as shown in the screenshot below. Additionally, you will be able to see more logs from Loop by enabling: "Action" -> "Include Info Messages" in Console's menubar settings.

[Ender-Wang]

Loop Keybinds.json

[mrkai77]

I see you mentioned cycling the current focus, but I’m not seeing any focus-changing actions listed in your keybinds file. Were you referring to a general cycle action?

If I put my pointer on the other screens (not on the screen where the focus window is), then cycle through the focus window, it moves to the next screen and is aligned to the left bottom edge of that screen, it's not positioned to the relative position of the original screen.

Could you also send a screen recording of this? I can’t reproduce the bug, so it’d be great to watch the steps visually.

[Ender-Wang]

By cycling I mean this:

When I press it multiple times, it cycles the focus window through my displays.

I can record a video if you want, if necessary.

[mrkai77]

Got it, no need for a video then.

Just to confirm I understand your setup correctly, with “Resize window under cursor” turned off:

When the mouse is on the same screen as the window:

• The selected screen starts on the same display as the window/cursor.
• "Next screen" behaves correctly and moves to the screen directly to the left.

When the mouse is on a different screen from the focused window:

• The selected screen still starts on the same display as the window/cursor.
• "Next screen" behaves incorrectly and instead moves to the bottom-left screen.

And when "Resize window under cursor" is on, the "Next Screen" action functions correctly in both cases.

Is that accurate?
Also:

• How many monitors do you have, and could you send a photo of their layout in System Settings?
• Do you remember the last version where this worked (either a version number or roughly when it was working)?

[Ender-Wang]

To ensure we are on the same page, here's a video I took.
https://github.com/user-attachments/assets/a9f95c8a-6ee0-483a-8f6b-2f29936ace4e

I cannot recall when it worked, but I tried a few builds till somewhere around build 148, which crashes with the keybinds I uploaded above. It might take some time to find which build works. I can try more after work.

My setup:

[Ender-Wang]

Additionally, on the current build 1.4.0 (1586) (and many builds before this one), the loop window shows up at the bottom left of the top right monitor in my setup when I first open it. I was opening it in the bottom display (the main one).

[mrkai77]

Please give this build a try: https://github.com/MrKai77/Loop/actions/runs/20706802576/artifacts/5021302008
It should hopefully fix this issue!

[Ender-Wang]

@mrkai77 It's fixed, thanks!