Mercurial > pidgin
comparison plugins/ChangeLog @ 404:3d94cc1dc424
[gaim-migrate @ 414]
It's a good thing I proofread things; otherwise, there would be a lot of
confused people when 0.9.20 comes out.
committer: Tailor Script <tailor@pidgin.im>
| author | Eric Warmenhoven <eric@warmenhoven.org> |
|---|---|
| date | Wed, 14 Jun 2000 02:12:25 +0000 |
| parents | 59d97cd251ff |
| children | ae7c762775cd |
comparison
equal
deleted
inserted
replaced
| 403:d6f02d7f78d8 | 404:3d94cc1dc424 |
|---|---|
| 22 back to normal. If any of that was confusing, it was confusing to me, | 22 back to normal. If any of that was confusing, it was confusing to me, |
| 23 too. I added a plugin, error.c, which should help clear things up. | 23 too. I added a plugin, error.c, which should help clear things up. |
| 24 | 24 |
| 25 There is a new event, event_quit, which signifies that gaim has exited | 25 There is a new event, event_quit, which signifies that gaim has exited |
| 26 correctly (i.e. didn't segfault). Also, after this event is called, all | 26 correctly (i.e. didn't segfault). Also, after this event is called, all |
| 27 plugins are removed, and their gaim_plugin_init function is called. | 27 plugins are removed, and their gaim_plugin_remove function is called. |
| 28 This behavior is different from previous versions; however, it is the | 28 This behavior is different from previous versions; however, it is the |
| 29 proper way of doing things, and should have no effect on current | 29 proper way of doing things, and should have no effect on current |
| 30 plugins. The reason event_quit exists despite plugins being removed at | 30 plugins. The reason event_quit exists despite plugins being removed at |
| 31 quit is because a plugin can be removed without gaim quitting. They are | 31 quit is because a plugin can be removed without gaim quitting. They are |
| 32 distinctly separate events. | 32 distinctly separate events. |