comparison ChangeLog.API @ 25343:ff883620d9d4

Thomas Gibson-Robinson noticed that the "saveable" attribute of a status type didn't actually do anything (and consequently "non-saveable" status types were being saved). A side effect of fixing this is that we have to change the behavior of purple_status_type_new() to default "saveable" to TRUE in order to maintain the current behavior. Fixes #8162
author Daniel Atallah <daniel.atallah@gmail.com>
date Tue, 20 Jan 2009 04:08:00 +0000
parents fbef4cf4c783
children efde7e6ed5f2 3687049b4faf f95aa2b14bec
comparison
equal deleted inserted replaced
25342:161d9bdcca3c 25343:ff883620d9d4
1 Pidgin and Finch: The Pimpin' Penguin IM Clients That're Good for the Soul 1 Pidgin and Finch: The Pimpin' Penguin IM Clients That're Good for the Soul
2
3 version 2.5.5 (??/??/2009):
4 libpurple:
5 Changed:
6 * purple_status_type_new now defaults "saveable" to TRUE.
7 This was necessary in order to maintain the current behavior
8 while fixing non-saveable statuses not to be saved.
2 9
3 version 2.5.4 (01/12/2009): 10 version 2.5.4 (01/12/2009):
4 perl: 11 perl:
5 Changed: 12 Changed:
6 * Purple::PluginPref->get_bounds no longer takes two integer 13 * Purple::PluginPref->get_bounds no longer takes two integer