view doc/notify-signals.dox @ 17697:ae7a4134e499

Changing this timer to run every 50 milliseconds instead of every 5 milliseconds. The timer is used to integrate our glib mainloop with silcclient's mainloop. Some Red Hat people complained that the timer causes the CPU to wake up really often and that hurts out power consumption on laptops and what not. Ideally the integration wouldn't need the timeout thing and would instead by event-driven. http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=242398
author Mark Doliner <mark@kingant.net>
date Mon, 04 Jun 2007 02:22:50 +0000
parents 8cf53d7a0887
children 2177a11e169d
line wrap: on
line source

/** @page conversation-signals Notification Signals

 @signals
  @signal displaying-userinfo
 @endsignals

 @signaldef displaying-userinfo
  @signalproto
void (*displaying_userinfo)(PurpleAccount *account, const char *who, PurpleNotifyUserInfo *user_info);
  @endsignalproto
  @signaldesc
   Emitted before userinfo is handed to the UI to display.
   @a user_info can be manipulated via the PurpleNotifyUserInfo API in notify.c.
  @note
    If adding a PurpleNotifyUserInfoEntry, be sure not to free it -- PurpleNotifyUserInfo assumes responsibility for its objects.
  @param account   The account on which the info was obtained.
  @param who       The screen name of the user whose info is to be displayed.
  @param user_info The information to be displayed, as PurpleNotifyUserInfoEntry objects
 @endsignaldef

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