On Wed, Jan 04, 2012 at 01:23:53PM +0100, Samuele Catusian wrote: > On Tue, Jan 03, 2012 at 10:51:00PM +0000, Thomas Adam wrote: > > On Tue, Jan 03, 2012 at 07:09:56PM +0100, Samuele Catusian wrote: > > > Everything works well, but just after the xrandr invocation all the > > > existing windows get replaced, and I have to manually fix their position > > > one by one. The same behaviour happens when deactivating the second > > > monitor. > > > > FVWM doesn't understand the XRandR protocol natively. If you bugger about > > with xrandr whilst FVWM is running, you must issue a Restart command to FVWM > > for FVWM to notice the change in screen resolution, etc. > > Sorry, I forgot to mention that important part: I actually issue an > > FvwmCommand Restart > > in my script just after the xrandr invocation, and this leds to the > windows displacement. IIRC, that command should indeed restart FVWM too, > right?
Yes, and the windows will be displaced like that because the windows are only ever recaptured with respect to their original geometry -- FVWM won't know to replace them unless you issue a "PlaceAgain" command as well, but this might not do what you'd expect it to. Basically, restarting FVWM for XRandR support is as good as you can hope for to pick up the new resolution; replacing windows based on the change of resolution is a tall order to implement in FVWM: I started it, but have not finished it. For now, you can either use PlaceAgain, or just restart X11 anf log in again with a new FVWM session. -- Thomas Adam _______________________________________________ fvwm-crystal-users mailing list fvwm-crystal-users@gna.org https://mail.gna.org/listinfo/fvwm-crystal-users
