search for: dbus_message_append_arg

...ge *message, + CompDisplay *d) +{ + DBusMessage *reply; + const char *pluginDir = PLUGINDIR; + const char *homePluginDir = HOME_PLUGINDIR; + const char *metadataDir = METADATADIR; + int version = ABIVERSION; + + reply = dbus_message_new_method_return (message); + + dbus_message_append_args (reply, DBUS_TYPE_STRING, &programName, DBUS_TYPE_INVALID); + dbus_message_append_args (reply, DBUS_TYPE_INT32, &version, DBUS_TYPE_INVALID); + dbus_message_append_args (reply, DBUS_TYPE_STRING, &pluginDir, DBUS_TYPE_INVALID); + dbus_message_append_args (reply, DBUS_TYPE_STRIN...

I am writing a configuration front end for the compiz gconf plugin at the moment, but it's proving harder than it should be because gconf does not record what type of compiz option the key is. For example, say i want a color picker for each color option the only way I can tell with gconf if it is color is if it has a # at the beginning, but there could be string option which also have a # at

...c0 in strlen () from /lib/libc.so.6 #1 0x00002aaaac1b0657 in dbus_watch_handle () from /usr/lib/libdbus-1.so.3 #2 0x00002aaaac197cc1 in dbus_set_error () from /usr/lib/libdbus-1.so.3 #3 0x00002aaaac19d6f1 in dbus_message_iter_append_basic () from /usr/lib/libdbus-1.so.3 #4 0x00002aaaac19ded9 in dbus_message_append_args_valist () from /usr/lib/libdbus-1.so.3 #5 0x00002aaaac19e265 in dbus_message_append_args () from /usr/lib/libdbus-1.so.3 #6 0x00002aaaac9fb565 in dbusAppendOptionValue (d=0x8, message=0x6714d0, type=7368532, value=0x6702f0) at dbus.c:673 #7 0x00002aaaac9fc0b3 in dbusSendChangeSignalForOption (d...