Mercurial > pidgin.yaz
view doc/sound-signals.dox @ 26816:c26c6d25142d
Don't try to process PEP events if it's not <message type='event'/>
I don't know why, but my personal account was receiving about 15
error responses from my Google Talk account's previously connected
resources (service-unavailable errors) and Pidgin was treating those as
legitimate notifications of events from the remote end, which is wrong.
author | Paul Aurich <paul@darkrain42.org> |
---|---|
date | Tue, 28 Apr 2009 01:04:14 +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