Mercurial > pidgin.yaz
view doc/gtkblist-signals.dox @ 30094:6797736dbe37
Does anyone know the purpose of the ui_write, ui_read and data_not_sent
FT UI callbacks? It looks like they allow a UI to decide how to safe
incoming file transfers? They're not used in Pidgin or Finch. Are
they used elsewhere?
Valgrind is complaining about an invalid free. I think it happens either
when the local user cancels a file transfer or when the remote user
cancels a file transfer. I think this change fixes it.
Revision fa4ce539e5025eb07aad3ca824cd4c512010d8a8 is related to these
callbacks and to this change by foufou33@ gee male dot com
The valgrind error is:
==23064== Invalid free() / delete / delete[]
==23064== at 0x4C24D68: free (vg_replace_malloc.c:325)
==23064== by 0x9293209: g_array_free (in /lib/libglib-2.0.so.0.2200.3)
==23064== by 0x95B1995: purple_xfer_priv_data_destroy (ft.c:71)
==23064== by 0x92AA5D1: ??? (in /lib/libglib-2.0.so.0.2200.3)
==23064== by 0x92AAE17: g_hash_table_remove_all (in /lib/libglib-2.0.so.0.2200.3)
==23064== by 0x92AAFC4: g_hash_table_destroy (in /lib/libglib-2.0.so.0.2200.3)
==23064== by 0x95B579C: purple_xfers_uninit (ft.c:1642)
==23064== by 0x95ACF08: purple_core_quit (core.c:238)
==23064== by 0x43EB3E: gtk_blist_delete_cb (gtkblist.c:227)
==23064== by 0x6F9A727: ??? (in /usr/lib/libgtk-x11-2.0.so.0.1800.3)
==23064== Address 0x2355f0e0 is not stack'd, malloc'd or (recently) free'd
author | Mark Doliner <mark@kingant.net> |
---|---|
date | Tue, 06 Apr 2010 09:52:27 +0000 |
parents | d75813811637 |
children |
line wrap: on
line source
/** @page gtkblist-signals GtkBlist Signals @signals @signal gtkblist-hiding @signal gtkblist-unhiding @signal gtkblist-created @signal drawing-tooltip @signal drawing-buddy @endsignals @see gtkblist.h <hr> @signaldef gtkblist-hiding @signalproto void (*gtkblist-hiding)(PurpleBuddyList *blist); @endsignalproto @signaldesc Emitted when the buddy list is about to be hidden. @param blist The buddy list. @endsignaldef @signaldef gtkblist-unhiding @signalproto void (*gtkblist-unhiding)(PurpleBuddyList *blist); @endsignalproto @signaldesc Emitted when the buddy list is about to be unhidden. @param blist The buddy list. @endsignaldef @signaldef gtkblist-created @signalproto void (*gtkblist-created)(PurpleBuddyList *blist); @endsignalproto @signaldesc Emitted when the buddy list is created. @param blist The buddy list. @endsignaldef @signaldef drawing-tooltip @signalproto void (*drawing-tooltip)(PurpleBlistNode *node, GString *text, gboolean full); @endsignalproto @signaldesc Emitted just before a tooltip is displayed. @a text is a standard GString, so the plugin can modify the text that will be displayed. @note Make sure to free @a *text before you replace it! @param node The blist node for the tooltip. @param text A pointer to the text that will be displayed. @param full Whether we're doing a full tooltip for the priority buddy or a compact tooltip for a non-priority buddy. @endsignaldef @signaldef drawing-buddy @signalproto char *(*drawing-buddy)(PurpleBuddy *buddy); @endsignalproto @signaldesc Emitted to allow plugins to handle markup within a buddy's name or to override the default of no formatting for names shown in the buddy list. @param buddy A pointer to the PurpleBuddy that will be displayed. @return The text to display (must be allocated), or @c NULL if no changes to the default behavior are desired. @endsignaldef */ // vim: syntax=c.doxygen tw=75 et