Go to file
Jonas Ådahl 81b28a1d97 kms: Notify about privacy screen changes via predictions
When we change the privacy screen, we added a result listener to the KMS
update object to notify the upper layer about the privacy screen state
change. This was slightly awkward as one might have changed the state
multiple times for a single update, thus it was necessary to remove any
old result listeners to an update before adding a new one.

Doing this will not be possible when updates are fully async and managed
by the KMS impl device.

To handle this, instead make the post-commit prediction notify about
changes that happens in response to a successfully committed update. We
already predicted the new privacy screen state, so the necessary change
was to plumb the actual change into a callback which emits the signal if
there actually was a privacy screen change.

This will then be communicated via the same signal listener that already
listens to the 'resources-changed' signal.

Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2340>
2022-07-25 11:02:35 +00:00
.gitlab/issue_templates gitlab: Add missing < in markdown comment tag 2020-02-14 03:10:28 +00:00
.gitlab-ci ci: Make run-tests.sh usable for the dist job too 2022-01-04 12:07:06 +01:00
clutter clutter: Let ClutterInputMethods pass the anchor position for preedit text 2022-07-19 11:04:56 +00:00
cogl cogl: Drop CoglHandleObject and CoglHandleClass 2022-05-31 16:28:16 -03:00
data monitor-manager: Add NightLightSupported property to DisplayConfig 2022-05-17 08:42:25 +00:00
doc doc: Add monitor configuration documentation 2022-01-25 16:25:48 +00:00
meson build: Check NEWS for version 2021-09-05 00:15:56 +02:00
po Update Nepali translation 2022-05-20 09:33:30 +00:00
src kms: Notify about privacy screen changes via predictions 2022-07-25 11:02:35 +00:00
subprojects build: bump ABI to sysprof-capture-4 2020-07-28 11:13:30 -07:00
tools tools/uncrustify: Remove space between i18n function shortcuts and ( 2021-12-09 20:59:49 +01:00
.gitignore wayland: Remove Gtk primary selection protocol 2022-05-18 20:15:08 +00:00
.gitlab-ci.yml ci: Update Wayland to v1.21.0 2022-07-14 22:29:56 +00:00
check-style.py ci: Avoid deadlock while reading uncrustify output 2021-08-23 17:40:43 +02:00
config.h.meson build: Add X11/XWayland config options 2022-05-25 16:42:04 +02:00
COPYING
HACKING.md docs: Update coding style link 2021-11-09 19:52:14 +01:00
meson_options.txt meson: Allow to build without gnome-desktop 2022-03-03 15:07:38 +00:00
meson.build build: Update Wayland dependency to 1.21 2022-07-14 22:29:56 +00:00
mutter.doap mutter.doap: Add marge-bot as a maintainer 2020-11-16 11:59:45 +01:00
NEWS Bump version to 43.alpha 2022-07-10 13:26:00 +02:00
README.md readme: Add links to the API documentation 2022-06-14 15:15:08 +00:00

Mutter

Mutter is a Wayland display server and X11 window manager and compositor library.

When used as a Wayland display server, it runs on top of KMS and libinput. It implements the compositor side of the Wayland core protocol as well as various protocol extensions. It also has functionality related to running X11 applications using Xwayland.

When used on top of Xorg it acts as a X11 window manager and compositing manager.

It contains functionality related to, among other things, window management, window compositing, focus tracking, workspace management, keybindings and monitor configuration.

Internally it uses a fork of Cogl, a hardware acceleration abstraction library used to simplify usage of OpenGL pipelines, as well as a fork af Clutter, a scene graph and user interface toolkit.

Mutter is used by, for example, GNOME Shell, the GNOME core user interface, and by Gala, elementary OS's window manager. It can also be run standalone, using the command "mutter", but just running plain mutter is only intended for debugging purposes.

Contributing

To contribute, open merge requests at https://gitlab.gnome.org/GNOME/mutter.

It can be useful to look at the documentation available at the Wiki.

The API documentation is available at:

Coding style and conventions

See HACKING.md.

Git messages

Commit messages should follow the GNOME commit message guidelines. We require an URL to either an issue or a merge request in each commit. Try to always prefix commit subjects with a relevant topic, such as compositor: or clutter/actor:, and it's always better to write too much in the commit message body than too little.

Default branch

The default development branch is main. If you still have a local checkout under the old name, use:

git checkout master
git branch -m master main
git fetch
git branch --unset-upstream
git branch -u origin/main
git symbolic-ref refs/remotes/origin/HEAD refs/remotes/origin/main

License

Mutter is distributed under the terms of the GNU General Public License, version 2 or later. See the COPYING file for detalis.