view doc/sound-signals.dox @ 24386:6e4979001d6d

The "processing" flag basically says "this connection is busy, don't destroy it yet, wait until it's done processing." I don't think there's any reason for us to set processing to TRUE just because we're connecting. I think this is a holdover from before our purple_proxy_connect() could be canceled. But now that it's cancelable, if we want to kill the connection we can cleanly cancel the connect without worrying about the callback being triggered.
author Mark Doliner <mark@kingant.net>
date Wed, 12 Nov 2008 09:10:29 +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