Mercurial > pidgin
view doc/sound-signals.dox @ 28749:819f464e581c
Make sure that libpurple core knows that a buddy is on the allow list just
after accepting their add request. Previously, this was not a problem, and
would go away at next login, but now that the core does its own client-side
blocking, it appears as if newly added buddies can't talk to you.
Fixes #10898.
author | Elliott Sales de Andrade <qulogic@pidgin.im> |
---|---|
date | Wed, 09 Dec 2009 03:02:03 +0000 |
parents | e0613cf8c493 |
children |
line wrap: on
line source
/** @page sound-signals Sound Signals @signals @signal playing-sound-event @endsignals @see sound.h <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.doxygen tw=75 et