view doc/sound-signals.dox @ 24199:aa8ddc4e12af

GtkBlist: don't set the Urgent hint whenever a connection error occurs or is updated In principle, setting Urgent is a good idea, because the user can tell that an error has occurred. However, it winds up being repeatedly re-set every time an account tries and fails to reconnect, which is incredibly annoying. I think the right solution is to keep a set of accounts we've set urgent for, removing them from the set when they successfully connect. But not setting it at all is better than the current state.
author Will Thompson <will.thompson@collabora.co.uk>
date Sun, 28 Sep 2008 17:19:38 +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