On Mon, 9 Apr 2012 at 22:51:21 +0200, Johann Haarhoff wrote: > Hi All > > I recently added a second screen to my setup, so now I finally have > to deal with the Xinerama/Xrandr features. I realise that the Xrandr > support for Xrandr is super basic (we are just restarting wmaker > when anything changes), but even so, I think I am seeing some > funnies. > > So I wonder if anybody can reproduce these and/or how you guys are > working around these? > > 1. > > Plug in external monitor, wmaker restarts as expected, but it > re-runs everything in ~/GNUstep/Library/WindowMaker/autostart . So > after a few plug/unplug cycles, I have multiple copies of nm-applet > etc. running. > > I can't really figure out how to work around this, except maybe > adding "--no-autolaunch" to the restarted copy. (See main.cpp:694), > and then making execInitScript() check for the flag (see > main.cpp:567). I can code this patch if it is the "right way", but > maybe there is a better way?
The proper solution would be to not restart wmaker in the first place, so I don't think this idea should be implemented. The Enlightment (e16) window manager does it right, it calls a function DeskRootResize() upon xrandr events. We should do the same. I don't have the time to do this now though. -- To unsubscribe, send mail to [email protected].
