a7c4e8cefa
The graphene functions used by clutter for picking assume that boxes are inclusive in both there start and end coordinates, so picking at y coordinate 32 for an actor with the height 32 placed at y coordinate 0 would still be considered a hit. This however is wrong as 32 is the first position that is not in the actor anymore. Usually this would not be much of a problem, because motion events are rarely ever at exactly these borders and even if they are there will be another motion event soon after. But since actors in gnome-shell usually are aligned with the pixel grid and on X11 enter/leave events are generated by the X server at integer coordinates, this case is much more likely for those. This can cause issues with Firefox which when using client side decorations, still requests MWM_DECOR_BORDER via _MOTIF_WM_HINTS to have mutter draw a border + shadow. This means that the Firefox window even when using CSD is still reparented. For such windows we receive among others XI_RawMotion and XI_Enter events, but no XI_Motion events. And the raw motion events are discarded after an enter event, because that sets has_pointer_focus to TRUE in MetaSeatX11. So when moving the cursor from the panel to a maximized Firefox window the last event clutter receives is the enter event at exactly integer coordinates. Since the panel is 32px tall and the generated enter event is at y position 32, the picking code will pick a panel actor and the focus will remain on it as long as the cursor does not leave the Firefox window. Fix this by excluding the bottom and right border of a box when picking. Fixes https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4041 Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1842> |
||
---|---|---|
.gitlab/issue_templates | ||
.gitlab-ci | ||
clutter | ||
cogl | ||
data | ||
doc | ||
meson | ||
po | ||
src | ||
subprojects | ||
tools | ||
.gitignore | ||
.gitlab-ci.yml | ||
config.h.meson | ||
COPYING | ||
meson_options.txt | ||
meson.build | ||
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 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.
Coding style and conventions
The coding style used is primarily the GNU flavor of the GNOME coding style with some additions:
-
Use regular C types and
stdint.h
types instead of GLib fundamental types, except forgboolean
, andguint
/gulong
for GSource ids and signal handler ids. That means e.g.uint64_t
instead ofguint64
,int
instead ofgint
,unsigned int
instead ofguint
if unsignedness is of importance,uint8_t
instead ofguchar
, and so on. -
Try to to limit line length to 80 characters, although it's not a strict limit.
-
Usage of g_autofree and g_autoptr are encouraged. The style used is
g_autofree char *text = NULL; g_autoptr (MetaSomeThing) thing = NULL; text = g_strdup_printf ("The text: %d", a_number); thing = g_object_new (META_TYPE_SOME_THING, "text", text, NULL); thinger_use_thing (rocket, thing);
-
Declare variables at the top of the block they are used, but avoid non-trivial logic among variable declarations. Non-trivial logic can be getting a pointer that may be
NULL
, any kind of math, or anything that may have side effects. -
Instead of boolean arguments in functions, prefer enums or flags when they're more expressive. The naming convention for flags is
typedef _MetaSomeThingFlags { META_SOME_THING_FLAG_NONE = 0, META_SOME_THING_FLAG_ALTER_REALITY = 1 << 0, META_SOME_THING_FLAG_MANIPULATE_PERCEPTION = 1 << 1, } MetaSomeThingFlags;
-
Use
g_new0()
etc instead ofg_slice_new0()
. -
Initialize and assign floating point variables (i.e.
float
ordouble
) using the formfloating_point = 3.14159
orratio = 2.0
.
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.
License
Mutter is distributed under the terms of the GNU General Public License, version 2 or later. See the COPYING file for detalis.