|Summary:||No documentation for dbus_glib_remote_object_object_info|
|Product:||dbus||Reporter:||Nathan Phillip Brink (binki) <ohnobinki>|
|Component:||GLib||Assignee:||Rob Taylor <rob.taylor>|
|Status:||RESOLVED NOTOURBUG||QA Contact:||John (J5) Palmieri <johnp>|
|i915 platform:||i915 features:|
Description Nathan Phillip Brink (binki) 2011-07-08 05:24:57 UTC
I see the following lines in xchat-2.8.8's src/common/dbus/dbus-plugin.c:init_dbus(): dbus_g_object_type_install_info (REMOTE_TYPE_OBJECT, &dbus_glib_remote_object_object_info); But I can't find any documentation on this mysterious dbus_glib_remote_object_object_info variable. I would like to know why it exists and what legal uses it has.
Comment 1 Simon McVittie 2011-07-11 04:58:31 UTC
(In reply to comment #0) > I see the following lines in xchat-2.8.8's > src/common/dbus/dbus-plugin.c:init_dbus(): > > dbus_g_object_type_install_info (REMOTE_TYPE_OBJECT, > &dbus_glib_remote_object_object_info); > > But I can't find any documentation on this mysterious > dbus_glib_remote_object_object_info variable. It's part of XChat, not dbus-glib. It's the "glue" used to export an object (a struct describing the object's methods, signals and properties), which is typically generated by dbus-binding-tool (although telepathy-glib contains a reimplementation of dbus-binding-tool which may be better for complex projects).