Currently, upstream is discussing how to implement notch support:
https://gitlab.freedesktop.org/wayland/wayland-protocols/-/issues/87
Regardless, Sxmo doesnt need this issue to be resolved upstream and we can work around notch issues in sway/dwm.
In sway, you can set the config to:
bar { gaps 42 0 }
and the area around the notch will just not be used to display anything. It works extremely well.
How do we want to include this in the default config? Do we want to create an environmental variable in the device profiles and how would we load that environmental variable in dwm and sway config?
Perhaps on a seperate file which will be called from dwm and sway config using
include
?
Seems to relate to #351 - Handling phone-specific sway configuration
I put mine to the bottom via
bar { position bottom }
as I have the same on my laptop devices. That doesn't solve nothing as the round display corners strip some of the information when the on-screen keyboard is disabled.With this configuration the notch and the display corners are an issue for the notifications, too.
The top-right part is hidden behind the round display corner, the top-left part hides behind the notch, you can't read anything.Thus, SXMO indeed does need this issue to be resolved upstream.
I think this could be a part of the deviceprofiles. Check scripts/deviceprofiles from sxmo-utils
Notches are an annoying thing to deal with for whatever goes in their place:( With Firefox bars or whatever app you have open is not worth coding a gap for In the top bar with a device specific profile sounds like a clean solution:)
we could add a variable in deviceprofile, telling how many characters are hidden by the notch. e.g. NOTCH="9" would add 9 characters between battery and wifi symbol like this: sxmobar -a notch 35 ooooooooo
which would be written to sxmo_hook_statusbar.sh
On Mon Jul 3, 2023 at 3:41 PM CEST, ~magdesign wrote:
we could add a variable in deviceprofile, telling how many characters are hidden by the notch. e.g. NOTCH="9" would add 9 characters between battery and wifi symbol like this: sxmobar -a notch 35 ooooooooo
That sounds like the easiest solution to me too. I do worry if sufficient space remains for all our icons then.
"~proycon" outgoing@sr.ht wrote:
On Mon Jul 3, 2023 at 3:41 PM CEST, ~magdesign wrote:
we could add a variable in deviceprofile, telling how many characters are hidden by the notch. e.g. NOTCH="9" would add 9 characters between battery and wifi symbol like this: sxmobar -a notch 35 ooooooooo
That sounds like the easiest solution to me too. I do worry if sufficient space remains for all our icons then.
I'm pretty much sure we can configure a blank space in Sway. This avoid the problem, without being satisfying. Only the composer could handle this.
what has to be solved is; when for example running vlc player it adds a symbol on top right, which moves everything to the left and the inserted empty notch space should shrink by this amount.
we are still stuck on this. while the swaybar gaps only provide
<amount>|<horizontal> <vertical>|<top> <right> <bottom> <left>
there is no solution from the compositor so far. https://man.archlinux.org/man/sway-bar.5as mentioned above we could add sensless symbols like
sxmobar -a notch 22 <-NOTCH->
and disable the tray icons also in ~/.config/sxmo/sway => Status Bar: section and just below position top add tray_output noneIts a hack, but at least the stuff is visible.
On Thu Apr 25, 2024 at 12:41 AM CEST, ~magdesign wrote:
as mentioned above we could add sensless symbols like
sxmobar -a notch 22 <-NOTCH->
and disable the tray icons also in ~/.config/sxmo/sway => Status Bar: section and just below position top add tray_output none Its a hack, but at least the stuff is visible.I agree it's better to have a hack than nothing at all. I submitted a simple patch in line with the above: https://lists.sr.ht/~mil/sxmo-devel/patches/51596