GitLab

676fea75 (comment 906088)

And deprecate old compositing-manager setting.

Reduced resources setting was used to disable minimize effect and
to show wireframe when moving or resizing windows.

Minimize effect still can be disabled by using enable-animations
setting from org.gnome.desktop.interface schema. And if you are
really trying to reduce resource usage you probably already have
animations disabled.

Wireframe mode has not been updated/fixed to work with CSD windows
and/or to exclude shadow/resize area from SSD windows. Also quickly
testing with and without compositor wireframe sometimes leaves
parts of frame on screen.

Considering that there has not been any bug report about broken
wireframe mode I think it is time to remove it instead of wasting
time trying to fix something that nobody is using.

GNOME Flashback will install GSettings override file to change
button-layout default value.

https://bugzilla.gnome.org/show_bug.cgi?id=769798

When using Metacity theme we don't need to realod it when
gtk-theme-name changes. It is needed only with GTK+ theme.

https://bugzilla.gnome.org/show_bug.cgi?id=757044

Display will be null when libmetacity-private will be used in
compiz.

This is needed to make sure that client-side and server-side
decorations have same button layout.

GNOME Settings Daemon will update Gtk/DecorationLayout from
button-layout. At this point everything should be ok.

But then it is possible to override Gtk/DecorationLayout from
xsettings plugin in GNOME Settings Daemon. At this point we can
end up with different button layouts between client-side and
server-side decorations. I can not think any reason why someone
would want different button layouts.

Move warning message about missing extensions required for
compositing from display.c to prefs. and display ths warning every
time user tries to enable compositing manager.

If required extension/extensions are missing return FALSE even
compositing-manager is enabled in preferences.

Rather than defining keybindings in static arrays generated at compile
time, store them in a hash table initialized in meta_display_init_keys()
and filled in init_builtin_keybindings().

This is a prerequisite for allowing to add/remove keybindings at runtime.

https://bugzilla.gnome.org/show_bug.cgi?id=663428

Based on mutter, mostly on this commit by Florian:
https://git.gnome.org/browse/mutter/commit/?id=d42a2a3c2741b8b44b48f83eb79a82fb4fcd5bbd

Compositing manager is enabled by default since commit
317c52fd, but default value was
not updated. Do it now.

Theme name == NULL - use current GTK+ theme.

It's hardcoded to false. Based on mutter commit:
https://git.gnome.org/browse/mutter/commit/src/?id=1c569c2d0e651215d2a468fd80a449588a4743ca

Based on a patch by Thomas Jaeger <ThJaeger@gmail.com>

Add app-menu button support in themes. This is done only to support
metacity theme format 3.5 version. Metacity will not show this
button!

Based on mutter commit:
https://git.gnome.org/browse/mutter/commit/?id=c2ea650b3c484312c14f69b8b245ab117ef7c6e1

This was added only to add support for metacity theme format
version 3.2.

Add a preference /apps/mutter/general/attach_modal_dialogs. When
true, instead of having independent titlebars, modal dialogs appear
attached to the titlebar of the parent window and are moved
together with the parent window.

https://bugzilla.gnome.org/show_bug.cgi?id=612726

NOTE: Patch copied from mutter and adapted for metacity.

1. Manually applied this patch:
https://github.com/SolusOS-discontinued/consortium/commit/b463e03f5bdeab307ceee6b969c681f29537c76d
2. Ported tile-preview.c to gtk3.

Adapted from patch by Chad Glendenin available at:
http://chad.glendenin.com/metacity/patch.html

Starting metacity gives the error Lib-GIO-ERROR **: Settings schema
'org.gnome.wm.keybindings' is not installed
which makes sense, since the actual keybindings are located at
org.gnome.desktop.wm.keybindings

https://bugzilla.gnome.org/show_bug.cgi?id=665168

Commit a228546d merged the visual-bell/visual-bell-type options,
but the change turned out too disruptive for gnome-control-center /
gnome-shell, so gsettings-desktop-schemas commit a5819b2a4e9 re-added
the separate option.

Move preferences to GSettings, using mainly shared schemas from
gsettings-desktop-schemas.

Unlike GConf, GSettings support is not optional, as Gio is already
a hard dependency of GTK+.

Based on an initial patch from Milan Bouchet-Valat.

https://bugzilla.gnome.org/show_bug.cgi?id=621204