view doc/sound-signals.dox @ 25432:256fbe98f6be

The jabber_register_parse function was looking for the <x> node as a child of the <iq> node instead of the <query> node. (See Chs 4 & 5 of XEP-0077) Somebody (maybe it'll be me?) should probably check that the code for these two cases does what it's supposed to, since I don't think it would have run before now. It also looks like the precedence may be wrong (See Ch 6).
author Elliott Sales de Andrade <qulogic@pidgin.im>
date Sat, 07 Feb 2009 23:45:18 +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