pablopunk / pablopunk/SwiftShift
Make Swift Shift only modify one window when size/move is in use
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 644
- Forks
- 31
- Avg merge
- 2m
- Merged PRs (30d)
- 4
Description
Bug description
If I'm resizing a window, and my cursor moves to a different window while still performing the resize interaction, the second window will take the move/resize gestures from the interaction.
I would expect all resize/move gestures to be performed on the first window I interacted with until I release all keys - even if that meant rejecting resize/move gestures that would be invalid for that window. Currently, it is possible to accidentally slip these gestures through to a lower window revealed by resizing.
Setup
I have CTRL set to move a window; CTRL+OPTION set to resize.
This means I can begin moving a window by tapping control, then additionally pressing option in the same interaction to resize a window (releasing it to go back to moving the window).
I have launch-at-login ON, but focus-on-window, use-quadrants, and snap-to-nearby-window all set to OFF.
macOS version
Tahoe 26.6.2
Settings
- [✓] Launch at login
- [ ✓] Show menubar icon
- [ ] Focus on window
- [ ] Use quadrants
- [ ] Snap to nearby window
Shortcuts
-
Move:
Keyboard: CTRL
Mouse: none -
Resize:
Keyboard: CTRL+OPTION
Mouse: none
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source files or tests are named. Start by tracing the move/resize interaction handling and reproduce the issue with CTRL for move and CTRL+OPTION for resize while crossing onto another window; done means all gestures in one interaction remain tied to the first window until the keys are released.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- swift
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100