mrkai77 / mrkai77/Loop

✨ Option to make Next/Previous display movement follow clockwise order

Open
#1,000 13 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Feature
Dominant language
Swift
Stars
11.6k
Forks
270
Avg merge
8h 7m
Merged PRs (30d)
3

Description

Bug Description

These are my display arrangements and the order I would expect when moving a window to the next / previous display in a clockwise direction, as illustrated below:

Image

In this layout, I expect the window to move between displays following the clockwise order shown by the numbered arrows.

Actual behavior

However, this is what actually happens:

Image

The window traversal order does not follow the physical clockwise arrangement of the displays and instead jumps between displays in an unintuitive order.

Affected Scope

User interface

Steps to Reproduce
  1. I think you may need at least 4 displays for test.
  2. Arrange displays in two lines.
  3. Move window to next display/previous display.
Reproducibility

Always

Expected vs Actual Behavior

Expected behavior

When moving a window to the next or previous display, the window should follow the physical display layout in a clockwise order.

Actual behavior

When moving a window to the next or previous display, the window moves between displays in a non-clockwise and unintuitive order.

Screen Recordings / Screenshots

No response

Severity

Critical (major functionality broken)

macOS Version

macOS 15.7.3

Loop Version

Version 🧪 1.4.1 (1673)

Did You Try the Development Build?

Yes

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 have looked to see if this is a duplicate of another bug report.
  • I can help with further investigation.
  • I can help with developing a fix for this issue.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the issue with at least four displays arranged in two lines, then test the Next and Previous display actions. Trace the display traversal behavior and compare it with the physical clockwise arrangement shown in the issue. Done means window movement follows that clockwise order in both directions without breaking other layouts.

Written by the indexing model from the issue text.

Assessment

Tech stack
macos, swift
Domain
desktop, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.