Mercurial > pidgin.yaz
view doc/dbus-server-signals.dox @ 20550:28493a27849b
Looking at purple_contact_set_alias and purple_blist_alias_contact functions
in blist.c, the only difference I see is that the latter function
notifies any existing conversation with the contact so that it can update
its title, while the former doesn't. I can't think of a reason why they
should behave differently, or why we should have both of them. I was going
to deprecate purple_blist_alias_contact in favour of purple_contact_set_alias,
but seeing we do purple_blist_alias_ for buddy and chats, I am deprecating
purple_contact_set_alias instead. OK?
author | Sadrul Habib Chowdhury <imadil@gmail.com> |
---|---|
date | Wed, 19 Sep 2007 10:01:45 +0000 |
parents | 1ec93dd2f359 |
children | e0613cf8c493 |
line wrap: on
line source
/** @page dbus-server-signals DBus Server Signals @signals @signal dbus-method-called @signal dbus-introspect @endsignals <hr> @signaldef dbus-method-called @signalproto gboolean (*dbus_method_called)(DBusConnection *connection, DBusMessage *message); @endsignalproto @signaldesc Emitted when a dbus method is going to be called. @param connection The DBus connection. @param message The DBus message. @return TRUE if signal handler handled the method. ??? @endsignaldef @signaldef dbus-introspect @signalproto void (*dbus_introspect)(GList **bidings_list); @endsignalproto @signaldesc ??? @param bindings_list ??? @endsignaldef */ // vim: syntax=c tw=75 et