view doc/notify-signals.dox @ 14261:bb060cdc23d1

[gaim-migrate @ 16943] Get rid of this thread stuff. You can read the whole saga at http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=201791 Basically we were working around some complicated library interactions between d-bus and newer, threaded versions of gnome-vfs. But the d-bus guys were awesome enough to make our working around unnecessary I'm seeing the following error printed to the console when I click on on the Send To menu in conversation windows, but I get this error with or without these threading changes. I'm not sure what's up with that. I should point out that our dnsquery.c stuff is calling g_thread_init() for both Unix and Windows now (it didn't used to do that on Unix) The error is: GLib-GObject: gsignal.c:1713: handler `982' of instance `0xc6d960' is not blocked committer: Tailor Script <[e-mail]>

/** @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