mrkai77 / mrkai77/Loop

✨ Setting that restricts “Resize window under cursor” to cursor usage

Open
#927 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Bug Description

I have enabled the Resize window under cursor option. The problem is that when I use a keyboard shortcut, I expect the focused window to resize but instead Loop resizes the window that is under the cursor (which may not always lie on the window in focus). The Resize window under cursor option should ideally apply only when Loop is being used with the mouse/trackpad.

This way whenever we are resizing multiple windows at once the Resize window under cursor option will be useful and whenever we are working on a particular window and later decide to maximize it we can simply use the keyboard shortcut without getting the mouse involved again.

Steps To Reproduce
  1. Enable Resize window under cursor option in Loop settings.
  2. Open two windows.
  3. Focus on one window but leave the cursor on the other window.
  4. Do any keybind to resize windows.
Expected Behavior

The keybind should make Loop resize the window in focus not the window under cursor.

Actual Behavior

Loop instead resizes the window under the cursor when using keybinds.

Screenshots

https://github.com/user-attachments/assets/07b46945-dc1f-4725-9321-d0edab510d2a

macOS Version

Sequoia 15.7.3

Loop Version

Version 1.3.0 (1528)

Additional Context

Perhaps instead of making a permanent behavioural change, adding this behaviour as a toggle would be better so that it can be used by keyboard centric, trackpad centric and mixed users alike to make the workflow tailored to their needs.

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).

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

No files, tests, or entry points are named in the issue. First reproduce the behavior with two windows, the cursor on one and keyboard focus on the other, then trace how Loop distinguishes keyboard shortcuts from mouse or trackpad resizing. Done means keyboard resizing targets the focused window while mouse or trackpad resizing can still target the window under the cursor.

Written by the indexing model from the issue text.

Assessment

Tech stack
macos, swift
Domain
desktop
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.