Hi ALL ...
I want to know the behaviour of gconf changeset api's.. ( I found as
non-atomic)..
when we do commitment by gconf_client_commit_changeset() ..the key values are
not updated in the Gconfdatabase instantly..
so if I read the same key just after commitment using gconf_client_get_*() ..
I get the non updated value from Gconf database..
I m using scratchbox environment (gconf-dbus 2.18.0.1..)
I think it may be because of client cache and gconf database synchronization
issue..
could anyone plz put a light on this issue and help me to solve the problem..
Thanks:
Umang Gupta
---------------------------------
Heres a new way to find what you're looking for - Yahoo! Answers _______________________________________________
gconf-list mailing list
[email protected]
http://mail.gnome.org/mailman/listinfo/gconf-list
