Skip to content
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.

Sign up for GitHub

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

Jump to bottom

FvwmPager: geometry string with @monitor not taken into account #310

Closed
ThomasAdam opened this issue Dec 3, 2020 · 0 comments
Closed

FvwmPager: geometry string with @monitor not taken into account #310

ThomasAdam opened this issue Dec 3, 2020 · 0 comments
Assignees
@ThomasAdam
Milestone
1.0.2

Comments

@ThomasAdam
Copy link
Member

When FvwmPager is asked to start up in a position on a specific screen, such as:

DestroyModuleConfig FvwmPager:*
*FvwmPager: Geometry 100x90-0+0@MONITORNAME

FvwmPager gets confused, and doesn't place the window on the correct monitor, even though the overall XxY geometry is correct.
@ThomasAdam ThomasAdam added this to the 1.0.2 milestone Dec 3, 2020
@ThomasAdam ThomasAdam self-assigned this Dec 3, 2020
ThomasAdam added a commit that referenced this issue Dec 3, 2020
@ThomasAdam
FvwmPager: fix geometry string values
3c42563 
When FvwmPager parses a geometry string with a monitor name embedded in
it, such as:

    *FvwmPager: Geometry 100x90-0+0@MONITORNAME

FvwmPager would not take into account MONITORNAME's dimensions, instead
defaulting to the current monitor.

This results from an incorrect use of global screen, vs specific screen.
Geometry strings are treated as the global screen, so FvwmPager needs to
use those values when calculating where to place its window.

Fixes #310
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ThomasAdam ThomasAdam

Labels
None yet
Projects
FVWM3
Status: Done
Milestone
1.0.2
Development

No branches or pull requests
1 participant
@ThomasAdam