You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Originally posted by patrick96 July 16, 2022
Polybar's struts can cover entire monitors if polybar is placed on a monitor that is in the middle of the X root screen. See also previous issues with tint2: https://gitlab.gnome.org/GNOME/mutter/-/issues/452
Ideally, WMs would compensate for that and only apply the parts of the struts which do not cover entire screens. However, many don't.
On the polybar side, the only conforming solution seems to be to just turn off struts.
For this, we should give the user an option in the bar section to enable/disable struts (enabled by default).
If struts are disabled, global/wm.margin-{top,bottom} being set, should produce a warning, because they are ignored.
The text was updated successfully, but these errors were encountered:
Hi, I would like to work on this. so, bar::reconfigure_struts() should be only be able to run if a new struts option is set to true ?
Is this the correct way to implement it?
Discussed in #2768
Originally posted by patrick96 July 16, 2022
Polybar's struts can cover entire monitors if polybar is placed on a monitor that is in the middle of the X root screen. See also previous issues with tint2: https://gitlab.gnome.org/GNOME/mutter/-/issues/452
There was also a report for this on reddit
Ideally, WMs would compensate for that and only apply the parts of the struts which do not cover entire screens. However, many don't.
On the polybar side, the only conforming solution seems to be to just turn off struts.
For this, we should give the user an option in the bar section to enable/disable struts (enabled by default).
If struts are disabled,
global/wm.margin-{top,bottom}
being set, should produce a warning, because they are ignored.The text was updated successfully, but these errors were encountered: