-
Notifications
You must be signed in to change notification settings - Fork 3
Automating Notch padding #159
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
When you say ends, are you talking about the bottom? Notching padding only affects the vertical padding. Horizontal padding is consistent across the whole app. |
Yes, the bottom |
Hm, I am wondering how this is being achieved though since the height between all notifications (and the simulated notch when no notification is present) is the same height. Are you by any chance using a custom resolution? |
No, I am not using a custom resolution. I am using the default settings of my MacBook's screen |
Strange. I’ll stay on the lookout for this issue. Until Henrik returns though… 🤷🏼♂️ |
Hi! |
Let me clarify, my issue is that the physical notch on my screen is exactly in between the 0px and 1px options. It's not an Alcove bug. I was just requesting a feature |
Ah I see. I haven't heard of this before but will forward to Henrik when he gets back. Can you provide the model of macbook you are using? |
I am using an M2 MacBook Air, thanks |
Problem
For me, the notch padding option is either 1 pixel too high or 1 pixel too short. If I set it to 0 pixels, when I use live activities the ends of the notch are slightly shorter and it triggers me, so I usually keep it at 1 pixel, but doing so the notch is slightly higher than it needs to be, and that triggers me too.
Expected behavior
My solution would be to add an option to automate notch padding. For example, I would set it to:
The text was updated successfully, but these errors were encountered: