Florian Müllner d6197b0904 background: Destroy redundant backgrounds right after loading ... When reacting to background settings changes, we may end up queuing more than one load. The redundant backgrounds are expected to be destroyed when the previous background has faded out; however since commit 933f38390b, the tweened actor is the same for all consecutive load operations and we end up with a single onComplete handler, ergo a single destroyed actor. As new backgrounds are always added to the bottom, we are not only piling up additional background actors, but break changing backgrounds more than once, as the correct background ends up being covered by previously added redundant actors. Fix this by destroying redundant actors right after loading rather than waiting for the fade animation to complete. https://bugzilla.gnome.org/show_bug.cgi?id=726120		2014-03-15 00:43:15 +01:00
..
extensionPrefs	Synchronize shell startup	2013-11-04 11:50:20 -05:00
gdm	authPrompt: Don't ever ask for a username if smartcard service is in foreground	2014-03-13 15:08:00 -04:00
misc	make NetworkManager optional	2014-02-11 18:04:44 -05:00
perf
ui	background: Destroy redundant backgrounds right after loading	2014-03-15 00:43:15 +01:00
js-resources.gresource.xml	Add indicator for location service being used	2014-01-28 18:39:12 +00:00
Makefile.am	make NetworkManager optional	2014-02-11 18:04:44 -05:00