Mercurial > pidgin
view doc/notify-signals.dox @ 15905:2cf21661f828
Cleanup and fixes for nat-pmp. We no longer do the whole 'try 10 times, doubling the delay in a blocking manner' ttempt from the original code; as I note in the comments above where the attempt is made a single time, this leads to about 8 minutes of nonresponsiveness if the router both doesn't support nat-pmp and doesn't send back a response to let the program know.
purple_pmp_create_map() and purple_pmp_destroy_map() now return a gboolean indicating success, as the internal data structures of nat-pmp are certainly not needed elsewhere.
The #includes are slightly reordered from the cleanup Mark did (thanks, Mark :) ), as with my OS X 10.3 cross-compiler, anyways, route.h needs to come after the sys includes to be properly handled.
author | Evan Schoenberg <evan.s@dreskin.net> |
---|---|
date | Sun, 25 Mar 2007 01:29:58 +0000 |
parents | faa6afdcea39 |
children | 8cf53d7a0887 |
line wrap: on
line source
/** @page conversation-signals Notification Signals @signals @signal displaying-userinfo @endsignals @signaldef displaying-userinfo @signalproto void (*displaying_userinfo)(GaimAccount *account, const char *who, GaimNotifyUserInfo *user_info); @endsignalproto @signaldesc Emitted before userinfo is handed to the UI to display. @a user_info can be manipulated via the GaimNotifyUserInfo API in notify.c. @note If adding a GaimNotifyUserInfoEntry, be sure not to free it -- GaimNotifyUserInfo 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 GaimNotifyUserInfoEntry objects @endsignaldef */ // vim: syntax=c tw=75 et