Mercurial > pidgin.yaz
view doc/gtkaccount-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 | 8cf53d7a0887 |
children | e0613cf8c493 |
line wrap: on
line source
/** @page gtkaccount-signals GtkAccount Signals @signals @signal account-modified @endsignals <hr> @signaldef account-modified @signalproto void (*account-modified)(PurpleAccount *account); @endsignalproto @signaldesc Emitted when the settings for an account have been changed and saved. @param account The account that has been modified. @endsignaldef */ // vim: syntax=c tw=75 et