GNOME Bugzilla – Bug 98426
use the global animation key /desktop/gnome/interface/enable_animations
Last modified: 2020-11-07 12:15:39 UTC
I already submitted an animation patch for metacity [1] which was rejected by Havoc. Now I noted that you added a boolean gconf key named "/apps/panel/global/enable_animations". My proposal is the following: We remove the "/apps/panel/global/enable_animations" key and move it to "/desktop/gnome/interface/enable_animation" as I'm sure that some people are annoyed by the animation when pressing a launcher (including me) AND by the metacity one. Using one keyname for all animations makes much more sense from a users' point of view. see you, Chris [1] http://bugzilla.gnome.org/show_bug.cgi?id=92867
Havoc: what do you think about this ? It sounds like it could be a good idea because we already have the option in the panel. Moreover it would be a more consistent behaviour.
A single global key certainly beats a key for each animation.
Commited a patch which adds enable_animations to /desktop/gnome/interface. Next thing I'll do is revamping my metacity patch. regs, Chris
*** Bug 102583 has been marked as a duplicate of this bug. ***
It seems like this has been committed, is it time to close the bug?
I'm not sure we're using this key in the panel...
No, obviously we don't. The toplevel panel property "animate" seems to be construct-only.
Besides, it isn't set from gconf.
Retitling; Manny, please doublecheck to see that I am correct.
2.13.x still uses the panel enable_animations key.
Let's add a milestone for this. Not sure it'll get in for 2.14.x, but we won't forget about it so easily. Also, should we follow the xsetting or the gconf key? If there's an xsetting, I guess this is what we should look...
bugzilla.gnome.org is being replaced by gitlab.gnome.org. We are closing all old feature requests in Bugzilla which have not seen updates for many years. If you still use gnome-panel and if you are still requesting this feature in a currently supported version of GNOME (currently that would be 3.38), then please feel free to report it at https://gitlab.gnome.org/GNOME/gnome-panel/-/issues/ Thank you for reporting this issue and we are sorry it could not be implemented.