Awn

Should Awn react live on GConf settings?

Asked by Timon_and_Pumba

Settings for Awn (and applets) are stored in GConf.
Should Awn, all its components and the applets react "live" on these settings?
Meaning, if you change a setting, should it have a direct effect on the operation of Awn?

This is important when one develops an applet and should be used consistently. I do not know
what performance impact it will have when every setting if read from Gconf if it is needed. The
other option is that the setting is cached, and only reread on startup of Awn.

Question information

Language:
English Edit question
Status:
Answered
For:
Awn Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Neil J. Patel (njpatel) said : 		#1

Yes, I am currently fixing bits of Awn that don't react to GConf, but you should always react to value changes. GConf even provides api so you know when the value has been changed outside of your program (ie. via gconf-editor), there is not a penalty because you don't have to poll for changes, events are send out by gconfd, and the library calls the specified function when something changes.

Revision history for this message
haytjes (h4writer) said : 		#2

I think it now reacts instantly (one issue with it is that the right functions isn't called to redraw it). There are only a couple of settings that needs a restart to take effect, but that is always mentioned in the graphical settings changer. I think for applets and other stuff it would be better that it is updated 'live'. I have also the feeling that gnome/kde or whatever wants it that way. If I'm on gnome and changes some settings in gconf-editor it does it immediately....

So I would stick to 'live' changing.

Can you help with this problem?

Provide an answer of your own, or ask Timon_and_Pumba for more information if necessary.

To post a message you must log in.