aboutsummaryrefslogtreecommitdiff
path: root/ChangeLog
diff options
context:
space:
mode:
authorTed Gould <ted@gould.cx>2012-02-14 11:50:12 -0600
committerTed Gould <ted@gould.cx>2012-02-14 11:50:12 -0600
commit40274af162593ec3c7e7887b455951621c5206b2 (patch)
treec23ba443b76c62e19e26e5801cd187e92b9a9bcb /ChangeLog
parentca8b36326725f529799187768caa436edd1465af (diff)
parenta820ba783386064dfa221586e0d0f9b0234d5be6 (diff)
downloadlibayatana-indicator-40274af162593ec3c7e7887b455951621c5206b2.tar.gz
libayatana-indicator-40274af162593ec3c7e7887b455951621c5206b2.tar.bz2
libayatana-indicator-40274af162593ec3c7e7887b455951621c5206b2.zip
* New upstream release.
* Visibility fixes for indicators using that functionality * Ensure that parent_object is more aggressively set * Fix memory leak on groups of items in desktop files
Diffstat (limited to 'ChangeLog')
-rw-r--r--ChangeLog81
1 files changed, 81 insertions, 0 deletions
diff --git a/ChangeLog b/ChangeLog
index db583ce..b80a919 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,5 +1,86 @@
# Generated by Makefile. Do not edit.
+2012-02-14 Ted Gould <ted@gould.cx>
+
+ 0.4.91
+
+2012-02-13 Lars Uebernickel <lars.uebernickel@canonical.com>
+
+ indicator_object_set_visible: only emit entry-{added,removed} when visibility actually changed
+
+ Emitting those signals is semantically incorrect. It also confused
+ indicator-loader and the panel, because they are not checking whether an entry
+ is already present in their entry-added handlers. This led to gtk warnings
+ ("widget already has a parent") and strange effects, such as the same menu
+ being added multiple times into the panel.
+
+ This patch also makes indicator_object_dispose use indicator_object_set_visible
+ (it was already doing something similar).
+
+2012-02-13 Lars Uebernickel <lars.uebernickel@canonical.com>
+
+ indicator_object_dispose: remove unneeded list of entries
+
+2012-02-13 Lars Uebernickel <lars.uebernickel@canonical.com>
+
+ indicator_object_dispose: use _set_visible instead of reimplementing it
+
+2012-02-13 Lars Uebernickel <lars.uebernickel@canonical.com>
+
+ indicator_object_set_visible: no need to check for ENTRY_INIT
+
+2012-02-12 Lars Uebernickel <lars.uebernickel@canonical.com>
+
+ indicator_object_set_visible: only emit entry-{added,removed} when visibility actually changed
+
+ Emitting those signals is semantically incorrect. It also confused
+ indicator-loader and the panel, because they are not checking whether an entry
+ is already present in their entry-added handlers. This led to gtk warnings
+ ("widget already has a parent") and strange effects, such as the same menu
+ being added multiple times into the panel.
+
+2012-02-10 Ted Gould <ted@gould.cx>
+
+ Free groupname after usage
+
+2012-02-09 Daniel d'Andrada <daniel.dandrada@canonical.com>
+
+ Plug memory leak in parse_keyfile function.
+
+2012-02-03 Ted Gould <ted@gould.cx>
+
+ Be more agressive in ensureing the parent_object value is available everywhere.
+
+2012-02-03 Marco Trevisan (Treviño) <mail@3v1n0.net>
+
+ tests, DummyIndicatorSignaler: free the allocated memory.
+
+2012-01-25 Marco Trevisan (Treviño) <mail@3v1n0.net>
+
+ Test loader: check also for parent changes
+
+2012-01-25 Marco Trevisan (Treviño) <mail@3v1n0.net>
+
+ Tests: update dummy signaler to work with real IndicatorObjectEntry
+
+ This fixes a crash due to the parent/unparent.
+
+2012-01-25 Marco Trevisan (Treviño) <mail@3v1n0.net>
+
+ IndicatorObject: update object parent in any case.
+
+2012-01-25 Marco Trevisan (Treviño) <mail@3v1n0.net>
+
+ Added better parent_object tests.
+
+2012-01-25 Marco Trevisan (Treviño) <mail@3v1n0.net>
+
+ Indicator-Object: update the parent_object value only if the entry is valid.
+
+2012-01-25 Marco Trevisan (Treviño) <mail@3v1n0.net>
+
+ IndicatorObject: correctly initialize the parent object.
+
2012-01-24 Ted Gould <ted@gould.cx>
0.4.90