This is useful to control which filter is enabled at startup, and
choose whether to have cumulative mode or a specific filter.

Moreover, cumulative mode is interesting only when a specific set of
filters was selected, as not all filters play well together.

This reverts commit 15aee719.

When Firefox brings itself back from being minimized, it forcefully
maps itself, and we failed to reparent it.  Fix this by reparenting any
managed windows that lacks a frame, even if we didn't ask for the map
ourselves.

The GSettings backend might have default values different from Compiz
when vendor overrides are in effect.

Having conflicting default values causes trouble, and is visible when
trying to set a setting to Compiz's default, which triggers a reset,
leading to set the value to the backend's default.  For example with a
boolean, this effectively locks the setting to its vendor override:
setting it to a different value makes it Compiz's default, triggering
a reset making it the backend's default.

This patch fixes it reading the default value from the backend, and
only using Compiz's own default if that read fails (backend has no
default, setting is unsupported, etc.).

Andrea Azzarone authored Jul 26, 2016 and Colomban Wendling committed Dec 13, 2018

This is a combination of the following commits which are the initial
change and successive fixups:
* 7226105a
* 9b56eb5b
* e492ac29
* 10266ad8

Sam Spilsbury authored Mar 03, 2016 and Colomban Wendling committed Dec 13, 2018

There was some confusion and incorrect casting going on which was
causing arbitrary memory to be overwritten. Don't do that.

This is a combination of the following commits which are the initial
change and successive fixups:
* 05faf1d0
* 86b01d72
* 260ef728

This makes the "show_desktop" feature work more naturally (show the
desktop whenever a relevant window is showing) instead of being a
global toggle state invisible to the user.

Add an option to choose whether to follow notifications, as well as
options to control for how long the notification is forcefully shown,
and the timeout until the focus goes back to the previous zoom location
if no other event happened.

Don't keep a list of the last 5 events as we only delivered the last
one anyway.

Instead, remove all non-notification events but the last one, but keep
all notification events as they should not get dropped by a larger
sequence.

This allows clients to get more context on the focus area.

The code to free the data returned by
atspi_accessible_get_relation_set() was utterly wrong, leading to both
leaking memory and attempting an invalid free (which luckily was caught
by g_object_unref()'s safeguards).