Re: Strategies for multiple gconf notifications


What kind of thing do you have that would change all the keys at the same time?  Are these keys calculated based off of a user setting?  Or do you expect a user to change all 20 keys in a row?


On 5/10/07, Murray Cumming <murrayc murrayc com> wrote:
If I have an intensive process that should be rerun in response to any
one of twenty configuration keys, how might I prevent my application
from re-running that process 20 times instead of just once, when
changing all the keys at one time.

I guess I could just append each notification key to a GList, and use a
g_timeout handler to notify my application about batches of changes, if
anything changed, at regular intervals.

Or is there some existing API or known strategy to deal with this

I've tried temporarily setting a "disabled" key but querying this
generally returns true well before the notifications have arrived.

Murray Cumming
murrayc murrayc com

gconf-list mailing list
gconf-list gnome org

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]