[telepathy-glib/master] Talk about notify::alias in TpContact preamble.
Will Thompson
will.thompson at collabora.co.uk
Wed Apr 1 07:50:12 PDT 2009
It's worth highlighting the obvious, in case someone's missed it.
Reviewed-by: Simon McVittie <simon.mcvittie at collabora.co.uk>
---
telepathy-glib/contact.c | 11 ++++++++---
1 files changed, 8 insertions(+), 3 deletions(-)
diff --git a/telepathy-glib/contact.c b/telepathy-glib/contact.c
index faf93ca..82ee36e 100644
--- a/telepathy-glib/contact.c
+++ b/telepathy-glib/contact.c
@@ -46,9 +46,14 @@
*
* An object representing a contact on a #TpConnection.
*
- * Contact objects are instantiated using
- * tp_connection_get_contacts_by_handle() or
- * tp_connection_get_contacts_by_id().
+ * Contact objects support tracking a number of attributes of contacts, as
+ * described by the #TpContactFeature flags. Features can be specified when
+ * instantiating contact objects (with tp_connection_get_contacts_by_id() or
+ * tp_connection_get_contacts_by_handle()), or added to an existing contact
+ * object with tp_connection_upgrade_contacts(). For example, a client wishing
+ * to keep track of a contact's alias would set #TP_CONTACT_FEATURE_ALIAS, and
+ * then listen for the "notify::alias" signal, emitted whenever the
+ * #TpContact:alias property changes.
*
* Note that releasing a #TpContact object might release handle references
* held by calling tp_cli_connection_call_request_handles(),
--
1.5.6.5
More information about the telepathy-commits
mailing list