Mercurial > pidgin.yaz
view doc/sound-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 | 1414e0e01dc5 |
children | e0613cf8c493 |
line wrap: on
line source
/** @page sound-signals Sound Signals @signals @signal playing-sound-event @endsignals <hr> @signaldef playing-sound-event @signalproto gboolean (*playing_sound_event)(PurpleSoundEventID event, PurpleAccount *account); @endsignalproto @signaldesc Emitted when libpurple is going to play a sound event. This can be used to cancel playing sound by returning TRUE. @param event The event this sound represents. @param account The account the sound is being played for. @return @c TRUE if the sound should not be played, or @c FALSE otherwise. @endsignaldef */ // vim: syntax=c tw=75 et