brl/mutter
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
Read-only mirror of https://gitlab.gnome.org/GNOME/mutter
31,186 Commits 187 Branches 380 Tags 94 MiB
C 98.9%
Meson 0.7%
Python 0.3%
4f68713020
Go to file
Carlos Garnacho 4f68713020 frames: Notify borders on first content resize 
This addresses the following race condition:
1. Window+MetaFrame are created non-fullscreen, _MUTTER_FRAME_EXTENTS
   is initialized through widget measuring, accounting for frame.
2. Window and MetaFrame become fullscreen.
3. MetaFrameContent gets first size allocation, already fullscreen.
4. Borders were initialized to 0,0,0,0, become set to 0,0,0,0 correctly
   reflecting fullscreen, however notify::borders is not emitted.
5. _MUTTER_FRAME_EXTENTS stays accounting for the frame extents.

It sounds sensible to have the borders initialized to a meaningful value,
so account for the first time the border would be set due to the content
being (re)sized, and let this first value trigger notify::borders resulting
in _MUTTER_FRAME_EXTENTS updates.

Since all later _MUTTER_FRAME_EXTENTS changes happen through content
resizes, we only have to cater for this initial handover between the
frame/content initialization paths done through widget measuring and
the later paths done through MetaFrameContent resizes.

Closes: https://gitlab.gnome.org/GNOME/mutter/-/issues/2937
Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3476>
2024-01-03 19:31:51 +00:00
.gitlab/issue_templates
.gitlab-ci ci: Look for matching ref in user remote for branch pipeline 2023-08-08 04:11:13 +02:00
clutter clutter/stage-view: Remove superfluous return in void function 2024-01-02 13:54:38 +00:00
cogl build: Make use of defined req variables 2024-01-03 12:09:46 +00:00
data Add debug controller 2023-12-01 14:25:08 +00:00
doc cogl/gir: Depend explicitly on Mtk 2023-11-03 11:27:52 +00:00
meson build: Replace custom post-install script 2022-11-19 02:21:05 +01:00
mtk mtk: Mark mtk_rectangle_to_graphene_rect in-variable as const 2023-12-29 12:45:19 +01:00
po Update Russian translation 2023-12-11 12:16:42 +00:00
src frames: Notify borders on first content resize 2024-01-03 19:31:51 +00:00
subprojects build: Update sysprof build options 2022-12-17 19:58:00 +00:00
tools Add debug controller 2023-12-01 14:25:08 +00:00
.gitignore Add .buildconfig to .gitignore 2023-02-17 21:44:29 +00:00
.gitlab-ci.yml ci: Mark our git clone as a safe directory 2023-12-13 11:09:32 +00:00
check-style.py ci: Mark the regex to find chunks in code style checks as regex string 2023-12-15 14:49:57 +00:00
config.h.meson build: One config file to rule them all 2023-11-15 12:00:19 +00:00
COPYING
HACKING.md Document trace span naming 2023-11-22 11:46:07 +00:00
meson_options.txt edid: Integrate libdisplay-info for edid parsing 2023-05-02 17:37:01 +00:00
meson.build build: Require libdrm >= 2.4.95 2024-01-03 14:46:04 +01:00
mutter.doap DOAP: Remove defunct mailing list; add Discourse 2023-09-15 03:19:22 +02:00
NEWS Bump version to 45.0 2023-09-16 22:51:03 +02:00
README.md readme: Add Mtk docs link 2023-09-02 10:50:47 +00:00

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 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.

If a commit fixes an issue and that issue should be closed, add URL to it in the bottom of the commit message and prefix with Closes:.

Do not add any Part-of: line, as that will be handled automatically when merging.

The Fixes tag

If a commit fixes a regression caused by a particular commit, it can be marked with the Fixes: tag. To produce such a tag, use

git show -s --pretty='format:Fixes: %h (\"%s\")' <COMMIT>

or create an alias

git config --global alias.fixes "show -s --pretty='format:Fixes: %h (\"%s\")'"

and then use

git fixes <COMMIT>

Example

compositor: Also consider dark matter when calculating paint volume

Ignoring dark matter when calculating the paint volume missed the case where
compositing happens in complete vacuum.

Fixes: 123abc123ab ("compositor: Calculate paint volume ourselves")
Closes: https://gitlab.gnome.org/GNOME/mutter/-/issues/1234

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.