Mercurial > pidgin
view doc/notify-signals.dox @ 17811:e62095e99db0
Add new function purple_xfer_get_remote_user.
Expose the xfer-functions to dbus.
Register the xfer's so dbus-scripts can play with them, and we don't get a
runtime dbus-whining.
author | Sadrul Habib Chowdhury <imadil@gmail.com> |
---|---|
date | Sun, 27 May 2007 21:35:47 +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