screenEdgeGapTopNotch doesn't appear to work
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 42/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- macos, swift
- Domain
- desktop, operating-systems
Research direction
Reproduce the maximize behavior on the built-in macOS display with screenEdgeGapTopNotch set to 0 and screenEdgeGapsOnMainScreenOnly toggled both ways, comparing it with the external monitor behavior. Trace how these settings affect the notch-area gap; done means the configured top gap is respected when the menubar is hidden without covering sketchybar.
Written by the indexing model from the issue text.
Description
macOS version: 15.6.1
Rectangle version: 0.91 (97)
By default on my mac I hide the menubar and have sketchybar live at the top of my screen. When I first started using rectangle, this presented an issue as the maximize window function would take up the entire screen when the menubar was hidden, thereby covering up sketchybar. This was an easy fix once I discovered the screenEdgeGap hidden setting. I added a 30px gap to the top and things worked fine when I plug into my external monitor at my desk.
The problem that I'm having is that on my built-in laptop display, macos seems to protect the notch area even when the menubar is hidden, so it will add 30px below the notch, even when the menubar is hidden. I looked at the docs and it seems like screenEdgeGapTopNotch should be the fix for this, but I've already set screenEdgeGapTopNotch to 0 and I still see the same behaviour. I have also tried setting screenEdgeGapsOnMainScreenOnly to true/false and still get the same behaviour.
Here is a screenshot of what happens on my built-in display when I use rectangle to maximize a window
- Dominant language
- Swift
- Stars
- 29.9k
- Forks
- 997
- Avg merge
- 4d 16h
- Merged PRs (30d)
- 13
Contributor 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 rxhanson/Rectangle
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 48/100
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 55/100
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 55/100
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 55/100
All issues in rxhanson/Rectangle
Similar issues
-
tvOS
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
skiptools/skip-fuse-ui#147 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
OneBusAway/onebusaway-ios#1438 · 1 reaction ·