delta/mutter.git/src/compositor/plugins, branch main

build: Use / operator instead of join_paths everywhere

2023-05-04T12:35:38+00:00

Part-of:

default-plugin: Handle unmanaging windows in switch_workspace

2023-02-01T15:21:55+00:00

Also add a regression metatest.

Closes: https://gitlab.gnome.org/GNOME/mutter/-/issues/2559
Part-of:

build: Make GTK dependency specific to X11

2022-12-22T14:13:54+00:00

Part-of:

default-plugin: Remove unnused field

2022-12-22T14:09:03+00:00

This drops the usage of GdkRGBA

Part-of:

compositor: Setup and use ownership chains

2022-12-17T14:13:48+00:00

As with the backend commit, this means all objects can reach the
MetaContext by walking up the chain, thus can e.g. get the backend from
the context, instead of the global singleton.

This also is a squashed commit containing:

compositor: Get backend via the context

The MetaCompositor instance is owned by MetaDisplay, which is owned by
MetaContext. Get the backend via that chain of ownership.

dnd: Don't get backend from singleton

window-actor: Don't get backend from singleton

dnd: Don't get Wayland compositor via singleton

background: Don't get the monitor manager from the singleton

plugins: Don't get backend from singleton

This applies to MetaPlugin, it's manager class, and the default plugin.

feedback-actor: Pass a compositor pointer when constructing

This allows getting to the display.

later: Keep a pointer to the manager object

This allows using the non-singleton API in idle callbacks.

Part-of:

plugin/default: Autostart localed when querying keyboard layout

2022-11-24T01:16:31+00:00

Otherwise it's required that systemd-localed is already running, which
is unlikely, since it will auto-terminate by default.

Fixes: 562024f746b5bcae7fcdd9cc2adac7a94f726110
Part-of:

plugin/default: Don't load properties when getting locale proxy

2022-11-01T21:04:21+00:00

This cuts away between 7 and 40 ms from the startup of tests.

Part-of:

default-plugin: Use stopped instead of completed signal

2022-09-20T17:14:53+00:00

The completed signal is only emitted if the timeline actually completed
but when an actor is destroyed or removed from its parent the timeline
is stopped and not completed.

The workspace switch effect removes window actors from the window group
which destroys the timeline so on_$EFFECT_effect_stopped is never
called and the pointer to the timeline is dangling.

Part-of:

default-plugin: Kill workspace switch animation on shutdown

2022-09-20T17:14:53+00:00

The workspace switch animation moves the WindowActors out of the
WindowGroup so if we shut down while the animation is playing the
WindowActors will have queued a destroy but will be disposed only after
the compositor is destroyed, leaving the WindowActor with a dangling
pointer.

Fix the issue by killing the workspace switch animation on shutdown.

Part-of:

default-plugin: Drop default confirm display dialog

2022-05-06T14:13:45+00:00

Mostly to drop the 1/3 use cases of zenity on mutter and usually
shells built on top of Mutter should implement that vfunc

Part-of: