Mercurial > pidgin.yaz
view doc/notify-signals.dox @ 16341:786edf5e2144
The core portion of the migration code. This is implemented as I described
in my e-mail a while back. If we have ~/.gaim and not ~/.purple (or we
have ~/.purple, but the "migrating" file exists, indicating an incomplete
previous migration), we copy all the files from ~/.gaim to ~/.purple and
move and symlink directories, except for plugins and icons. For icons,
we move and symlink any subdirectories, as a special case for the Album
plugin (written by me).
For this to work, it needs to be called by the UIs. Also, the icon
migration code is not included in this commit, so I highly recommend you
not test this on your main .gaim directory if you want a clean migration.
author | Richard Laager <rlaager@wiktel.com> |
---|---|
date | Mon, 23 Apr 2007 16:57:12 +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