6 Commits

Author	SHA1	Message	Date
Ryan Lortie	a8b5353b14	Add g_settings_sync() and use it	2010-06-10 22:30:44 -04:00
Ryan Lortie	3160bcad6a	GDBusConnection.call(): add 'reply_type' argument ... This allows the caller to specify the reply type that they are expecting for this call. If the reply comes back with the wrong type, GDBus will generate an appropriate error internally. - add a GVariantType * argument to g_dbus_connection_call() and _call_sync(). - move the internal API for computing message types from introspection data to be based on GVariantType instead of strings. Update users of this code. - have GDBusProxy pass this calculated GVariantType into g_dbus_connection_call(). Remove the checks done in GDBusProxy. - Update other users of the code (test cases, gdbus-tool, GSettings tool, etc). In some cases, remove redundant checks; in some other cases, we are fixing bugs because no checking was done where it should have been. Closes bug #619391.	2010-05-24 17:00:04 -04:00
Ryan Lortie	849684e540	GSettings tool: work-around GDBus issue ... There is currently no way (near as I can tell) to ensure that a message has been sent when using GDBus. If we exit() before we are sure, then it is very possible that the message isn't sent at all. This behaviour was observed when using the GSettings commandline tool with dconf. A quick and dirty workaround for now.	2010-05-17 07:16:37 -04:00
Matthias Clasen	f3e04973e7	Rename gsettings-tool to gsettings ... And make it verb-based.	2010-04-22 01:17:02 -04:00
Matthias Clasen	bedf4c3259	Add documentation and translation for gsettings-tool	2010-04-20 22:55:15 -04:00
Matthias Clasen	1dbe06c30a	Add a minimal commandline utility to poke GSettings	2010-04-20 22:55:15 -04:00