Mercurial > pidgin
view doc/notify-signals.dox @ 17226:5059a0a071a2
Restore the protocol specific URL handlers in purple-url-handler for those
protocols that don't have their own uri-handler signal handler in libpurple
yet. These can be phased out as protocols get their own uri-handler support,
after reading other C uri parser implementations I didn't want to tackle
that just yet.
author | Stu Tomlinson <stu@nosnilmot.com> |
---|---|
date | Fri, 25 May 2007 00:46:16 +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