view doc/gtklog-signals.dox @ 22640:23fe481afccf

The next version of RFC 3920, the draft of which can be found at http://www.xmpp.org/internet-drafts/draft-saintandre-rfc3920bis-04.html, and subsequent email clarifications with Peter Saint-Andre and Alexey Melnikov indicate that we should be trying the next mechanism in line after one mechanism fails. We should also be ensuring that the mech list is sorted in order of descending security, which we don't do yet; however, servers are supposed to send us a sorted list, as well, so this isn't a major issue. committer: Evan Schoenberg <evan.s@dreskin.net>
author Stu Tomlinson <stu@nosnilmot.com>
date Sun, 13 Apr 2008 06:37:47 +0000
parents e0613cf8c493
children
line wrap: on
line source

/** @page gtklog-signals GtkLog Signals

 @signals
  @signal log-displaying
 @endsignals

 @see gtklog.h

 <hr>

 @signaldef log-displaying
  @signalproto
void (*log_displaying)(PidginLogViewer *viewer, PurpleLog *log);
  @endsignalproto
  @signaldesc
   Emitted when a log is being displayed.
  @param viewer The log viewer
  @param log The log being displayed
 @endsignaldef

*/
// vim: syntax=c.doxygen tw=75 et