✨ Add 'Ignore notch' option for consistent top padding across screens

[kjvdven]

Adds an defaults write option "Ignore notch". When enabled, the notch height is subtracted from the top padding on notched displays, so the effective distance from the screen's top edge matches non-notch displays.

Users can enable with:

defaults write com.MrKai77.Loop ignoreNotch -bool true

Reset with:

defaults delete com.MrKai77.Loop ignoreNotch

Users with an external menu bar (e.g. SketchyBar) and the system menu bar hidden experience inconsistent top padding between notched and non-notch displays. On a notched MacBook, NSScreen.visibleFrame reserves space for the notch (~32pt), and the external bar padding stacks on top of that — resulting in more top gap than on an external monitor.

When "Ignore notch" is enabled, applyToBounds subtracts screen.menubarHeight from totalTopPadding (clamped to 0), compensating for the notch reserve. Backward-compatible: custom Codable init defaults ignoreNotch to false for existing configs.

Fixes #691

How has this been tested?

Tested on a MacBook Pro (notch) with an external monitor, system menu bar hidden, SketchyBar as external bar with 40px external bar padding configured in Loop.

• External monitor: top padding remains 40px as configured
• defaults write com.MrKai77.Loop ignoreNotch -bool true: top padding matches external monitor (40px from screen top)
• defaults delete com.MrKai77.Loop ignoreNotch: top padding is 40px + notch height (existing behavior)
• Existing configs without the new field load correctly (defaults to false)

macOS 15, Loop built from develop branch.

Checklist:

• I have performed a self-review of my own code
• I have made corresponding changes to the documentation if applicable
• I have no unrelated changes in this PR.

Please describe to which degree, if any, an LLM was used in creating this pull request.

This change was developed with assistance from Claude (Anthropic). The approach (subtracting screen.menubarHeight from top padding when the toggle is enabled) was designed collaboratively — the math and edge cases were worked through together, and all code was reviewed, understood, and tested by the contributor on a real notch + external monitor setup.

[mrkai77]

Thanks for the PR! Overall, this works well and the logic is correct. However, I think ignoreNotch belongs as a global setting rather than on PaddingConfiguration.

A couple of reasons:

1. It's a hardware/setup concern, not a padding preference. Whether to compensate for the notch is a property of the user's display setup, not a specific padding configuration. Conceptually it fits better as a global toggle (e.g. Defaults[.ignoreNotch]). Given that this is a fairly niche setup (hidden menu bar + external bar + notch display), I'd lean toward making it a defaults write option rather than a visible UI toggle. This also avoids adding complexity to the settings UI for something most users won't need.
2. It avoids the custom Codable conformance. Right now the PR replaces the auto-synthesized Codable with a manual init(from:) just to default ignoreNotch to false for existing configs. Pulling the flag out into a separate Defaults key lets PaddingConfiguration go back to synthesized conformance, keeping it clean.

[kjvdven]

Thnx for the review,

1. I changed the code to work with a default write instead of a UI toggle.
2. Removed the custom Codable conformance

[mrkai77]

Thank you!

[cyb3rko]

@kjvdven Does that still work for you?
I can not get it to work somehow :(

[kjvdven]

@kjvdven Does that still work for you? I can not get it to work somehow :(

Have you set the variable in the terminal?

defaults write com.MrKai77.Loop ignoreNotch -bool true

[cyb3rko]

Have you set the variable in the terminal?

I have, but I can not see any changed behaviour.
Any other setting that is required for that option to work?

[mrkai77]

@cyb3rko could you check if the macOS window manager is enabled in the Advanced tab? That setting can interfere with this feature. Also, make sure you’re running the latest development version :)

[cyb3rko]

Well, call me stupid.
I just realized that it's not included in 1.4.2, works now on pre-release version 👍.

Thanks to both of you