"Raimund Steger" <r...@mytum.de> writes: > On Wed, January 20, 2016 14:56, Thomas Adam wrote: >> [...] >> But that's a much larger piece of work, believe me. But your patch > > No argument here, but from [1], section 8: > > " > Clients MAY select for ConfigureNotify on the root window to be > informed of screen changes. This may be advantageous if all your > client needs to know is the size of the root window, as it avoids > round trips to set up the extension. > " > > I don't see how this could be understood in any other way than that it > /is/ acceptable for clients to handle ConfigureNotify even when not > setting up Xrandr. > > > [1] http://cgit.freedesktop.org/xorg/proto/randrproto/tree/randrproto.txt
As a follow up on this, I applied the patch and added some stderr prints. Then I used xrandr to change screen size, like this: xrandr -s 1024x768 xrandr -s 1600x1200 I found that xrandr generates configurenotify events. I got 2 root window configurenotifys for issuing the command once. But Fvwm doesn't react well. Fvwm sees the event and knows the new screen size but doesn't move anything around like it should. I told Fvwm to execute a "recapture" and that helped. I think if fvwm becomes aware of a new screen size, it makes sense to re-position all the windows and icons. -- Dan Espen
