4.14.2

See merge request GNOME/gtk!7096

Post-release version bump

See merge request GNOME/gtk!7097

This reverts commit 144cd2d9.

This commit is causing problems when using GTK 4.14 with
Pango 1.51.

Fixes: #6606

Revert "gsk: Avoid some allocations"

See merge request GNOME/gtk!7101

This reverts commit 3d898af7.

The commit caused a regression where, depending on the update policy,
we would not apply value changes at all.

Fixes: #6599

Fix a bug where a zero increment would make the value unsettable,
when the more natural operation is to allow any value to be set.

This was requested by Alexandre Franke.

Fixes: #6609

Revert "gsk: Avoid some allocations"

See merge request GNOME/gtk!7106

The job priority strings need context to disambiguate them from
similar short strings elsewhere.

printing: Add context to some strings

See merge request GNOME/gtk!7108

vulkan: Handle generating mipmaps for 1x1 images

Closes #6553

See merge request GNOME/gtk!7073

(cherry picked from commit 460eaac1)

9fe9ea34 vulkan: Handle generating mipmaps for 1x1 images
3080e297 gpu: ceil() offscreen size before generating offscreen
02d78176 demo: Use get_fps() in fishbowl demo

Merge branch 'wip/otte/for-main' into 'main'

See merge request GNOME/gtk!7122

The parsing for a `GTK_TYPE_SHORTCUT_ACTION` on a GtkShortcut in a
builder file can fail, resulting in a `NULL` GtkShortcutAction. This
currently does not result in any warnings, potentially making typos in
builder files tricky to debug.

Since `gtk_shortcut_action_parse_builder()` already sets an error if it
fails, we can just use that and simply return false.

builder: Show warning for invalid action on GtkShortcut

See merge request GNOME/gtk!7123

Fixes gnome-control-center#2994

Remove duplicate descriptions of the switch's appearance, describe more
particularly how the default signal handler for `GtkSwitch::state-set`
behaves, and add a suggestion that the `state` property should
only be set when communicating a delayed state change.

Fixes #6600

GtkShortcutManager allows adding controllers to it. For the default
implementation, they get added to one of two models, based on the
propagation phase (either GTK_PHASE_CAPTURE or GTK_PHASE_BUBBLE).

However, when a controller is removed, its presence in the manager gets
checked against the current propagation phase of the controller, which
may have changed from when it was added. This can lead to crashes if the
controller was not disposed properly since it still has a reference in
one of the two models of the GtkShortcutManager.

To fix this, add a callback for `notify::propagation-phase`, which
removes the controller from all possible models and readds it again with
its current phase. This callback is only disconnected permanently when
the controller is manually removed with
`gtk_shortcut_manager_default_remove_controller()`.

Closes #6246

This drops cursor and eraser source names to account for their removal
from GdkInputSource so that GDK_DEBUG=input debug message correctly
prints source type in X11 environment.

Fixes: c1d90273 ("gdk: Drop GDK_SOURCE_ERASER")
Fixes: 3285f52d ("gdk: Drop GDK_SOURCE_CURSOR")
Closes: #6619

dispose can be called more than once, so be safe for that.

Add the generated gdk headers to the sources for all the backends,
to guarantee that they are generated before the library is used.

Fixes: #6618

If there somehow end up being no `supported_versions`, `ctx` would end
up being dereferenced before being initialised. While I think that’s
unlikely, the compiler doesn’t know that, so let’s just initialise the
variable unconditionally.

Signed-off-by: Philip Withnall <pwithnall@gnome.org>

The compiler (gcc 13.2) thinks that `t` could be used uninitialised.
That’s obviously not the case, because there’s always going to be at
least one loop iteration due to the initial values of `t1` and `t2`.

Change the loop to a `do…while` to make that a bit clearer to the
compiler without making any functional changes to the code.

Signed-off-by: Philip Withnall <pwithnall@gnome.org>

Use docs.gtk.org for all the documentation that is hosted there.

Use the same types in the declaration of gsk_standard_contour_init.

Fixes: #6628

Don't clear the same pointer twice.

- Fix link to the security policy
- Drop the confusing note about SSH access (with the old URL)
- Use modern idiomatic Meson subcommands for configuring and building
- Use `git switch` instead of `git checkout`
- Specify that you should always use merge requests, not patches
- Link to the handbook instead of the wiki

In fetch_net_wm_check_window(), before updating the wmspec_check_window, a
check is performed to verify a 15s difference between last_wmspec_check_time
and the current monotonic time.

The comment suggests that this check is done to ensure that it doesn't check
for a new check window repeatedly over and over again. While that was the case
origionally, currently the last_wmspec_check_time only gets updated when
wmspec_check_window is set, which is already checked earlier, making the time
check useless.

This check causes issues on cold boots where gtk4 applications are not able
to obtain the wmspec_check_window until 15 seconds after boot, making gtk
unable to check for extended wm_hints during that time.

Fixes: #6558

Various cherry-picks for GTK 4.14

See merge request GNOME/gtk!7150