view doc/sound-signals.dox @ 26806:e07c066b3172

don't uninit accounts until savedstatus and status are uninited, this was never a problem until aff70668336849d4b1513fd8577f4d2a276d2520 which cleaned up accounts (which is itself a good thing) but savedstatus was using the uninitialized accounts (which is a bad thing) mtn using people probably want to check their status.xml for corrupted entries
author Ka-Hing Cheung <khc@hxbc.us>
date Tue, 28 Apr 2009 19:10:04 +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