view doc/sound-signals.dox @ 17576:d495103dcf88

Two questions: 1. XMPP <status> messages inside <presence> broadcasts should be plaintext and not HTML, right? 2. 'stripped = purple_markup_strip_html(str)' is basically the same as 'purple_markup_html_to_xhtml(str, NULL, &stripped)', right? This fixes a bug Emily found where setting an XMPP status message with an embedded link would drop the link completely. For example, in Pidgin you set your away message and insert a link so that the message body is <a href="http://www.example.com/">Example</a>. When we set this message for an XMPP account it just strips the HTML and sets the message to "Example". This change causes the message to be "Example (http://www.example.com/)". It's the same thing we do when displaying links in tooltips in the blist.
author Mark Doliner <mark@kingant.net>
date Sun, 10 Jun 2007 15:58:23 +0000
parents 1414e0e01dc5
children e0613cf8c493
line wrap: on
line source

/** @page sound-signals Sound Signals

 @signals
  @signal playing-sound-event
 @endsignals

 <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 tw=75 et