fvwmorg / fvwm3

FVWM version 3 -- the successor to fvwm2
Other
515 stars 78 forks source link

EwmhStruts - Does not affect entirety of X screen, only specific monitor #271

Closed MidFavila closed 3 years ago

MidFavila commented 4 years ago

When using EwmhStruts in 2.6.9 and early builds of FVWM3, EwmhStruts normally behaves in a "global" manner, affecting the entire X screen. In the latest git pull, however, it only appears to affect one monitor (the leftmost?) in regards to horizontal reservations.

I use a triple-head configuration; DP-0, DP-1, and DP-2, with DP-0 as the leftmost head, 1 in the middle, and 2 on the right. However, the following string only produces reserved space on the right side of DP-0; in prior versions, it would have reserved that space on DP-2.

EwmhBaseStruts 0 137 32 0

Vertical reservation, in this case the topmost 32 pixels, does work globally. Let me know if any more information or clarification is needed.

issue-label-bot[bot] commented 4 years ago

Issue-Label Bot is automatically applying the label bug to this issue, with a confidence of 0.93. Please mark this comment with :thumbsup: or :thumbsdown: to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

lgsobalvarro commented 4 years ago

You can define a EwmhBaseStruts for each monitor:

EwmhBaseStruts DP-0 foo EwmhBaseStruts DP-1 foo EwmhBaseStruts DP-2 0 137 32 0

MidFavila commented 4 years ago

Alright, this is my bad, then. I didn't see anything marked in the changelogs; since this is expected behavior and not a bug, I'll close the issue now.

Thanks.

MidFavila commented 4 years ago

After adjusting my configuration file with the suggested syntax, EwmhBaseStruts simply ceases to function at all; if I'm still in error, could you provide a pointer to the relevant section of the manual for myself and others in the future?

lgsobalvarro commented 4 years ago

My bad, I gave you the wrong syntax:

EwmhBaseStruts screen DP-X foo

MidFavila commented 4 years ago

So, upsides and downsides to report. The issue with screen specification and syntax was a me not staying up to date thing; however, the issue with specifying horizontal reservations remains.

Using the following string, I can successfully manipulate boundaries along the top and bottom of my rightmost display; however, horizontal boundaries still fail to apply.

EwmhBaseStruts screen DP-2 0 137 32 0

The same exact string specified with my leftmost monitor (DP-0) also fails to apply horizontal boundaries.

Oddly, they only seem to apply when the screen is not specified; please advise next steps.

ThomasAdam commented 4 years ago

Hi @MidFavila

Hmm. So if I set:

EwmhBaseStruts screen Virtual-1 0 150 50 0
EwmhBaseStruts screen Virtual-2 0 0 0 0

Then what I see (when I use xterm) on both monitors when I maximize them, is a fully-maximized xterm on Virtual-2, and a window on Virtual-1 which is 150 from the right, and 50 from the top. See the screenshot below. Am I missing something obvious here? Note that I do not have Style * ResizeHintOverride set which means regardless of having a bottom strut of 0 set, there will always be a slight gap.

fvwm3-example

MidFavila commented 4 years ago

After running over the issue some more on IRC, I'm putting up the details of my XRandR configuration and the FVWM3 debug log, as requested.

log.txt xrandr_out.txt