view doc/sound-signals.dox @ 22933:d464485a2bfc

Clean up the comments about MSNP14, and make the --enable-msnp14 option no longer commented out. This makes it possible, with stock pidgin, to build with msnp14 using --enable-msnp14 - are we ready for this? (my thought being that if we are ready for this we can see what happens when "early adopters" turn it on and maybe, just maybe, making msnp14 default for 2.5.0)
author Stu Tomlinson <stu@nosnilmot.com>
date Wed, 14 May 2008 01:57:45 +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