Mercurial > pidgin
view doc/notify-signals.dox @ 14001:66d01a547603
[gaim-migrate @ 16586]
It is feasible that a UI is finished with notifying the user via the Notification API within the UI callback and has no need of a ui_handle to deal with closing the notification at a later date nor to tell the gaim core at a later point that it is finished with the data.
If the ui_op for a notification returns a ui_handle of NULL, the GaimNotifyCloseCallback (if non-NULL) is now called immediately and the info structure is freed.
If the op returns a non-NULL value, which is the case for all of gtkgaim's functions, the behavior is unchanged.
committer: Tailor Script <tailor@pidgin.im>
author | Evan Schoenberg <evan.s@dreskin.net> |
---|---|
date | Thu, 27 Jul 2006 20:02:57 +0000 |
parents | 216988c717da |
children | faa6afdcea39 |
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, char **infotext); @endsignalproto @signaldesc Emitted before userinfo is handed to the UI to display. @a infotext is a pointer to a string, so a plugin can replace the text that will be displayed. @note Make sure to free @a *infotext before you replace it! @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 infotext A pointer to the userinfo text to be displayed. @endsignaldef */ // vim: syntax=c tw=75 et