-
-
Notifications
You must be signed in to change notification settings - Fork 84
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
Windows open outside of screen #85
Comments
Hi @afhp-2020, Weird. I cannot reproduce this either. Can you maybe take a video capture of the problems you're seeing here, and with #68 just so I can see what's going on visually? Presumably I'm missing a piece of setup from what you've described, but can't tell what that might be. EDIT: Can you also checkout
... and then run
Thanks. |
I can't reproduce #68 (and it was at best just a guess), let's forget it. Just to be sure, I wiped the fvwm3 build directory completely and re-cloned it (a few minutes ago), and rebuilt as described in your message.
Any place where I could drop the screencap ? |
You should be able to.zip it up and attach it here. Failing that, email it to me: [email protected] |
Is there any chance these applications (emacs, pidgin, etc.) are starting iconfied? What if you did:
In place of |
Started an Emacs on right screen, didn't show. As above, at FvwmConsole
Performing a relative move with |
Hi @afhp-2020, OK. I'm having problems reproducing your problem, but that's a good thing since it means you're using something I'm not. Can you shove the following at the top of your FVWM3 config file:
... and then can you send me the logs of FVWM3 to STDERR? I need everything, so if you wanted to make FVWM3 log to a separate file, that makes sense:
Thanks, |
fvwm3-master20200525.log.txt Of course I had to mis-name the logfile and only see it after upload... Same scenario (more or less) with master and with ta/gh-84:
Excellent work :) |
Thanks, @afhp-2020 -- I'll close this now. |
Another regression, may or may not be related to #68 ?
As of recently, and without apparent pattern, some windows will start opening outside the display. They didn't before,
and once they start they always do.Currently observed with one specific contact window in Pidgin, and just now with Emacs.
xsession-error log:
The window does appear in the window list, and one can check that it did open, in FvwmConsole:
Next (Emacs) Echo $[w.x] $[w.y]
will logPrimary screen is 1920 px wide, right screen (rotated) is 900 px wide, window is positioned just outside of the viewable area.
The window can be brought back from the FvwmConsole with e.g.
Next (Emacs) Move pointer
, but it's annoying.I haven't seen a pattern as to why it starts happening, but I've been juggling WMs and graphics drivers configurations lately, that probably doesn'h help.EDIT:
It would seem that this only happens when opening a window with the pointer on the right-hand monitor. Windows are positioned normally when the pointer is on the primary.
The FvwmConsole
Move pointer
command will work including when the pointer is on the right-hand monitor.Still, in the case of the Pidgin contacts: with Pidgin's contact list as well as the pointer on the right-hand monitor, the chat window for one contact will open normally (on the right-hand monitor) while the window for another (always the same) will open outside of the display area.
The text was updated successfully, but these errors were encountered: