Commits on Source (11)
-
Jürgen Benvenuti authored
-
Carlos Garnacho authored
This gives greater control to the callers on the place where a grab is being activated, this may make a difference in the handling of crossing events triggered through it, e.g. by having callers rely on having already obtained a ClutterGrab prior to handling the resulting effects. The "input only" grab has also been turned inactive by default, in order to to have the ClutterGrab pointer available for checks at the MetaWaylandEventHandler focus changing methods triggered through grab activation. (cherry-picked from commit 8e5f3a1f) Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3874>
-
Carlos Garnacho authored
Add the _inactive suffix, so that the state of these objects is clear. (cherry-picked from commit 01444e80) Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3874>
-
Chao-Hsiung Liao authored
-
Robert Mader authored
And stop pre-computing values, making errors like this harder to spot. The values 0.0625 (16/256) and 0.5 (128/256) were slightly off, resulting e.g. in "black" not being #000000 but #010001 RGB instead. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3906> (cherry picked from commit dfa5238b)
-
Jonas Ådahl authored
This means that for X11 sessions we'll do it before any windows are mapped, and before any plugin implementation is started. Doing it before a plugin is started is important, because things that the plugin does during startup can have consequences on how compositing on Xorg works. For the Xwayland case, we'll do it relatively in the setup phase. It appears to have been harmless to do it later in the post-opened signal, but there is no harm in doing it as one of the earlier steps. Closes: https://gitlab.gnome.org/GNOME/mutter/-/issues/3089 Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3329>
-
Jonas Ådahl authored
It's X11 specific, so put it in the X11 display manager object. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3329>
-
Jonas Ådahl authored
The test never noticed that the second instance never actually managed to load; it was looping a multi second retry session trying to redirect windows, meaning it failed to catch https://gitlab.gnome.org/GNOME/mutter/-/issues/3089. Fix the test so that it always waits for mutter to finish loading successfully, just like it waits fro the first. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3329>
-
Jonas Ådahl authored
Simply to make it clear that the renamed function is specific to a particular X11 initialization mode (mandatory Xwayland), put that in the name, so that it's easier to understand when this function is relevant. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3329>
-
Florian Müllner authored
Update NEWS.
-
Jeremy Bícha authored
This diff is collapsed.