Top |
TpSvcInterfaceInfo describes a dbus-glib-style GInterface in sufficient detail to export it on a GDBusConnection.
const TpSvcInterfaceInfo *
tp_svc_interface_peek_dbus_interface_info
(GType g_interface
);
See whether the given interface has Telepathy code generation data attached.
Since 0.99.10
void tp_svc_interface_set_dbus_interface_info (GType g_interface
,const TpSvcInterfaceInfo *info
);
Declare that g_interface
implements the given D-Bus interface, with the
given vtable. This may only be called once per GInterface, usually from
a section of its base_init function that only runs once.
This is typically only used within generated code; there is normally no reason to call it manually.
g_interface |
The GType of a service interface |
|
info |
struct encapsulating the GDBusInterfaceInfo, the GDBusVTable
and the GLib signal names corresponding to D-Bus signals.
The GDBusVTable methods must expect the object
implementing |
Since 0.99.10
GDBusInterfaceSkeleton * tp_svc_interface_skeleton_new (gpointer object
,GType iface
);
Return a GDBus interface skeleton whose methods and signals
are implemented by iface
on object
, and whose properties
are implemented by a TpDBusPropertiesMixin on object
.
struct TpSvcInterfaceInfo { volatile gint ref_count; GDBusInterfaceInfo *interface_info; GDBusInterfaceVTable *vtable; gchar **signals; };
The necessary glue between a dbus-glib-style TpSvc
GInterface
and telepathy-glib.
These structs are intended to be programmatically-generated.
volatile gint |
currently -1 since these structures can only be statically allocated; will be used for the reference count in the same way as GDBusInterfaceInfo if necessary |
|
GDBusInterfaceInfo * |
the GDBus interface information |
|
GDBusInterfaceVTable * |
the GDBus vtable, which must expect the object that
implements the |
|
gchar ** |
a |
[array zero-terminated=1] |
Since 0.99.10