8e2587c197
If we finish compositing in time, the composited result will be submitted prior to the deadline timer is triggered, and we'll be fine, and if not, at least the cursor updates will be smooth, which makes it appear smoother than not. There is a risk that this can negatively impact composited updates when moving the cursor, so make it possible to toggle a paint-debug flag for now until this has been more tested. This also mean we need to disarm the deadline timer after handling update, as there might be a scheduled cursor update pending, but we already handled it, so disarm the timer. Here is an illustration of the difference. In the following scenario, with disarming, the composited frame E, and the cursor movement C gets presented. With this branch, only the cursor movement C gets presented. ``` * A: beginning of composited frame * B: begin notification reaches KMS thread * C: cursor moved * D: calculated deadline dispatch time (disabled with the branch) * E: KMS update posted * F: KMS update reaches KMS thread * G: actual deadline (and with branch and gets committed) Compositor thread: --------A---------------E--------- \ \ \ \ KMS thread: -----------B------C----D---F-G---- ``` In the following scenario, by not disarming, the cursor update C will be presented, and the would-be-delayed composited frame E would be delayed anyway, i.e. fixing cursor stutter. ``` * A: beginning of composited frame * B: begin notification reaches KMS thread * C: cursor moved * D: calculated deadline dispatch time (and with branch will be dispatched) * E: KMS update posted * F: actual deadline * G: KMS update reaches KMS thread (and with branch gets postponed) Compositor thread: --------A---------------E--------- \ \ \ \ KMS thread: -----------B------C----D-F-G------ ``` Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3184> |
||
---|---|---|
.gitlab/issue_templates | ||
.gitlab-ci | ||
clutter | ||
cogl | ||
data | ||
doc | ||
meson | ||
mtk | ||
po | ||
src | ||
subprojects | ||
tools | ||
.editorconfig | ||
.gitignore | ||
.gitlab-ci.yml | ||
check-style.py | ||
config.h.meson | ||
COPYING | ||
logo.svg | ||
meson.build | ||
meson_options.txt | ||
mutter.doap | ||
NEWS | ||
README.md |
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 of 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 first look at the GNOME Handbook and the documentation and API references below first.
Documentation
- Coding style and conventions
- Git conventions
- Code overview
- Building and Running
- Debugging
- Monitor configuration
API Reference
- Meta: https://mutter.gnome.org/meta/
- Clutter: https://mutter.gnome.org/clutter/
- Cogl: https://mutter.gnome.org/cogl/
- CoglPango: https://mutter.gnome.org/cogl-pango/
- Mtk: https://mutter.gnome.org/mtk/
Meetings
There are recurring meetings to discuss development of GNOME Shell, mutter and related components.
License
Mutter is distributed under the terms of the GNU General Public License, version 2 or later. See the COPYING file for detalis.