view doc/sound-signals.dox @ 28672:7e2e95508a3a

Do not create a conversation yet. A plugin can stop a conversation from being created by intercepting the receiving-*-msg signals. But this code would always open a conversation if a '/buzz' is received as the first message. So we end up with an empty conversation window that we didn't create, and it's confusing as poop! Interestingly, I noticed this because the clang-analyzer cried about it. So yay clang-analyzer!
author Sadrul Habib Chowdhury <imadil@gmail.com>
date Mon, 28 Sep 2009 17:39:33 +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