view doc/sound-signals.dox @ 31072:3fad1d9e0bc3

Quote the path for the windows "run at startup" registry key. The only reason it ever worked like it was is that MS apparently has some wacky fallbacks that makes it find stuff in the Program Files folder when it sees a directory called "Program". Thanks to Christian Lange for noticing and tracking down the problem. Fixes #12781
author Daniel Atallah <daniel.atallah@gmail.com>
date Tue, 26 Oct 2010 18:52:56 +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