✨ Resizing adjacent windows
Maintainers usually reply within 1 day
@mrkai77 is already working on this.
Since Mar 24, 2024.
Assessment
This issue has not been assessed yet.
Description
Feature Request Description
When using macOS's split-view feature, the ability to adjust the middle divider for dynamic window resizing is quite useful, as demonstrated here:
https://github.com/MrKai77/Loop/assets/2030968/a6a5d008-5c15-40fb-b0a9-98289d43caa2
It would be cool if similar logic can be supported by Loop. Here's what I envision for this feature:
- Dynamic Window Resizing: Adjusting the size of one window should cause adjacent windows to resize accordingly, maintaining its alignment.
- Unified Adjustment for Shared Borders: Windows hidden behind the active window, which share a border with the resized window, should also resize dynamically. This creates a consistent layout and alignment.
- Padding Support: Adjustments should respect user-defined padding settings to maintain the visual consistency and usability of the workspace.
A potential implementation could involve user-adjustable virtual grid lines. Currently, the default possible grid (excluding the "Almost Maximize" setting) looks something like the following if I'm not mistake.
As an example, if a window is snapped to the Top Left Third and the user resizes it downward, all windows within this cell should reflect the change. Moreover, future window snaps would adhere to the adjusted layout. Here's what a 2 x 3 layout adjustment might look:
In terms of how Loop will detect and respond to window resizing actions would still be up for discussion. You could listen to window resizing events from the OS or implement a custom solution making use of preview windows, which might better reflect the impact of the resize on all windows.
I'm keen to hear your thoughts on this proposal and whether it aligns with your vision for Loop's evolution.
Screenshots
No response
Additional Context
No response
Final Checks
- My issue title is descriptive
- This is a single feature request (multiple feature requests should be reported individually)
- Dominant language
- Swift
- Stars
- 11.9k
- Forks
- 287
- Avg merge
- 17h 7m
- Merged PRs (30d)
- 5
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
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.
More from mrkai77/Loop
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
Maintainers usually reply within 1 day
-
🐞 Crash when editing the search field in the keybind action pickerPossibly taken @NicoCorini claimed this 10 days ago. OpenBug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
mrkai77/Loop#1187 · 4 comments ·
Maintainers usually reply within 1 day
-
Bug
Difficulty 4/5 3-5 days Newbie friendliness 25/100
Maintainers usually reply within 1 day
-
Bug
Difficulty 4/5 3-5 days Newbie friendliness 55/100
mrkai77/Loop#1191 · 1 reaction ·
Maintainers usually reply within 1 day
-
✨ Prioritize Custom Trackpad Gestures Over Default Radial Menu GesturesPossibly taken @mrkai77 claimed this 16 days ago. OpenFeature
Difficulty 4/5 3-5 days Newbie friendliness 25/100
mrkai77/Loop#1177 · 1 reaction ·
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
swiftlang/swift-markdown#299 ·
-
area: agents follow-up
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
manaflow-ai/cmux#37234 · 1 comment ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
bug product / functions
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 61/100
JWhite212/SignalLadder#215 ·
Maintainers usually reply within 1 day