-
-
Notifications
You must be signed in to change notification settings - Fork 82
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
FvwmPager ignores "Monitor" setting on the second monitor (shared mode) #611
Comments
Hi @NsCDE This seems to work OK for me? Here's what I have:
|
Hi @ThomasAdam I see the bug immediately. For a better visibility, this was what I used:
Monitor Virtual-2 is non-primary secondary. On the page 0 0 of both monitors I have windows. If I put "Monitor Virtual-1" (primary) in the configuration above, then I see window representations in pager, but with "Monitor Virtual-2" I got empty page altrough there ARE windows on Virtual-2 page 0 0. If I "walk" all 4 pages in pager, there is no windows on them in pager, but they should be there on 0 0. |
AFAICT, this should be fixed by PR #978 -- @somiaj has done some excellent work to improve this situation. From the testing I've done so far this seems to have resolved this. I'll mark this as closed once that PR has been merged, and if you find any other problems with FvwmPager and shared mode, please open specific bug reports. |
fvwm3 --version
)fvwm3 1.0.5 (1.0.4-16-g3663d42d)
Debian 11
Expected Behaviour
In "shared" DesktopConfiguration mode, FvwmPager, when called with "Module" should read "Monitor" line in configuration and select desk in the FvwmPager on Monitor where pointer is.
Actual Behaviour
FvwmPager in "shared" DesktopConfiguration mode, when calling it with the pointer on non-primary monitor pops up with the name and background (but not the windows) of the desk on primary monitor. This behaviour stops once desk is changed on second monitor for the first time. Switching back to primary monitor and calling FvwmPager there, resets this normalization, and bug can be triggered again as described.
The text was updated successfully, but these errors were encountered: