On Thu, 2007-07-19 at 11:07 +0200, Vincent Untz wrote: > Hi Pascal, > > Le jeudi 12 juillet 2007, à 11:25 +0100, Pascal Schoenhardt a écrit : > > The "engine" will be the majority of the code. It will be responsible > > for the storing, loading, and managing user profiles in GConf, and for > > interfacing with the Xrandr library directly to apply changes. It will > > also be responsible for writing changes to the xorg.conf file, when > > necessary. > > Is it really needed to write to xorg.conf? It'd be better to avoid doing > something requiring some privileges. Indeed, what's the use case of this? Should be perfectly possible to store the randr settings to apply in gconf and send the randr requests to the server when appropriate (just like done to set input device properties, which is why you can get a warning dialog when your GNOME keymap setting differs from the one your server uses (the one stored in xorg.conf)). afaik xrandr is about *not* storing information in xorg.conf, but discover it at runtime... Nicolas
Attachment:
signature.asc
Description: This is a digitally signed message part