Mercurial > pidgin
view plugins/mono/BooPlugin.boo @ 13905:4e44ecb866bd
[gaim-migrate @ 16394]
msn_session_sync_users() iterates over the buddy list, following the ->next pointers of the groups, contacts, and buddies. msn_show_sync_issue(), if called, removed the buddy for which it was called, in preparation for the buddy either being added to the server list or confirmed-to-be-removed. This could lead to the buddy pointer being released and ->next therefore being junk.
The buddy is now not removed until the user responds to the action dialog presented via msn_show_sync_issue(). I'm unclear why gtkgaim got away with this exercise in memory stomping but Adium/libgaim crashed every time, but it's safer in any case.
I also changed some foo->bar to gaim_foo_get_bar().
committer: Tailor Script <tailor@pidgin.im>
author | Evan Schoenberg <evan.s@dreskin.net> |
---|---|
date | Sun, 02 Jul 2006 09:37:25 +0000 |
parents | a3302d271199 |
children |
line wrap: on
line source
import Gaim class BooPlugin(GaimPlugin): def handle(*args as (object)): b as Buddy b = args[0] Debug.debug(Debug.INFO, "booplugin", "Boo Plugin knows that " + b.Alias + " is away\n") override def Load(): Debug.debug(Debug.INFO, "booplugin", "loading...\n") BuddyList.OnBuddyAway.connect(self, handle) override def Unload(): Debug.debug(Debug.INFO, "booplugin", "unloading...\n") override def Destroy(): Debug.debug(Debug.INFO, "booplugin", "destroying...\n") override def Info(): return GaimPluginInfo("Boo Plugin", "0.1", "Test Boo Plugin", "Longer Description", "Eoin Coffey", "urled")