Mercurial > pidgin.yaz
view doc/notify-signals.dox @ 14329:479164e18f1a
[gaim-migrate @ 17024]
If you loaded this plugin and activated one of the color preference check
boxes but never actually set a color choice you could cause gtk to crash when
it failed to understand a color setting of "". This is really a gtk+ bug since
they shouldn't crash on that but this workaround was easy and sensible.
I just added some minimal sanity checking to the values returned from
gaim_prefs_get_string (non-NULL and non-empty), it isn't perfect but it solves
the simple case.
committer: Tailor Script <tailor@pidgin.im>
author | Etan Reisner <pidgin@unreliablesource.net> |
---|---|
date | Thu, 24 Aug 2006 20:25:57 +0000 |
parents | 216988c717da |
children | faa6afdcea39 |
line wrap: on
line source
/** @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