view doc/buddyicon-signals.dox @ 11052:8a68c933a5dd

[gaim-migrate @ 12990] Patch #1227165 from sadrul This patch probes plugins when the plugin page is loaded in preferences. This allows users to activate newly installed plugins without restarting Gaim. The only way I can see this being a problem is if you installed a plugin which was version-compatible but binary incompatible. (For example, you're working on Gaim HEAD and change a public struct in a way that's binary backwards incompatible, build a plugin against it, install the plugin, and open the preferences page of a running copy of Gaim from before the change.) Even then, depending on the particular plugin and binary incompatibility, you might have to activate the plugin before Gaim would crash. So, unless I'm missing something, this should be safe. Let's see how it goes. committer: Tailor Script <[e-mail]>

/** @page buddyicon-signals Buddy Icon Signals

 @signals
  @signal buddy-icon-cached
 @endsignals

 <hr>

 @signaldef buddy-icon-cached
  @signalproto
void (*buddy-icon-cached)(GaimBuddyIcon *icon, GaimBuddy *buddy, const char *filename, const char *old_icon);
  @endsignalproto
  @signaldesc
   Emitted when a buddy icon is cached.
  @param icon     The icon that was just cached.
  @param buddy    The buddy the icon belongs to.
  @param filename The full filename for the newly created icon cache file.
  @param old_icon The filename of the icon cache file for the buddy's previous icon, or @c NULL if the buddy
                  had no icon when this new icon was set. This filename is generally the full filename of the
                  previous icon cache file, but if the previous buddy icon was set in an old version of Gaim,
                  this may just be the basename of the icon cache file. The directory can be obtained with
                  gaim_buddy_icons_get_cache_dir().
 @endsignaldef
*/