From: Felix M. <f.m...@we...> - 2004-03-09 09:12:13
|
Am Monday 08 March 2004 23:29 schrieb Kim Woelders: > Did you consider simply using different directories using -econfdir, as > I previously suggested? I did, but for this I would need to know the resolution before e is started= ,=20 and then call it from a wrapper script. After an automatic restart by the=20 epplet to be, the new resolution would be known, but I don't know how to=20 probe this from the command line on first startup. And e does this probe=20 anyway, so why not use it? And is there a way to tell e to restart with a=20 different confdir? > Maybe the only things that need to differ are the saved window settings > (...e_session-XXXXXX.snapshots.*)? maybe, this remains to be seen. When I simply restarted e after a resolutio= n=20 change, the backgrounds also weren't quite right. I don't know if that=20 information is stored in the same file. > - When the resolution is changed using xrandr E detects this and > restarts (or maybe just reconfigures?). > I'm not familiar with RandR but I assume this requires handling of some > new X events. > Or did you intend to tell E to change the screen resolution and restart? The latter. There's a command-line program for xrandr, it's quite simple to= =20 use. I was thinking of converting this into an epplet that restarts e=20 whenever it changes the resolution. This nicely circumvents the=20 event-handling. (Which is probably way over my head, as I said.)=20 > A few pointers: > Start out from current CVS. > Start in: =A0 =A0 =A0 =A0 =A0 =A0main() :) > Screen size: =A0 =A0 =A0 =A0 SetupX() > Load saved settings: LoadSnapInfo() > Load configuration: =A0LoadEConfig() That will get me started. I will probably tinker with it a little over the= =20 next weekend. Thanks, =46elix |