Remove all the old 2.x and 3.x version annotations.
GTK+ 4 is a new start, and from the perspective of a
GTK+ 4 developer all these APIs have been around since
the beginning.

Best to be consistent.

This may be useful for applications using render nodes.

Load random strings from /usr/share/dict/words instead of reusing the
same 10 words all the time. That way, we get closer to the real world
use case of having a full alphabet.

This way, we get a special no-copy case for resources.

https://bugzilla.gnome.org/show_bug.cgi?id=790270

Obviously gdk_device_get_history() is not the right function to change. To
delete if anything...

It only applies to GDK_MOTION_NOTIFY events, so this is a more descriptive
name. Also add Since tag in docs, and GDK_AVAILABLE_IN_3_94.

Not all the variables were renamed.

Daniel Stone authored Aug 23, 2017 and Emmanuele Bassi committed Feb 05, 2018

Before running gtk-query-immodules, the cache output directory may not
actually exist. Make sure it does before we try to write into it.

https://bugzilla.gnome.org/show_bug.cgi?id=793182


Signed-off-by: Daniel Stone <daniels@collabora.com>

The standard Vulkan SDK ships with a pkg-config file, like a modern
library should.

We should fall back to finding the library and header only for platforms
where pkg-config is not really a thing.

Based on a patch by: Daniel Stone <daniels@collabora.com>

https://bugzilla.gnome.org/show_bug.cgi?id=793181

The GDK_POINTER_MOTION_HINT_MASK enumeration value is gone, but we're
still keeping around the "is_hint" field in GdkEventMotion, even though
every backend sets it to `false` — except for the core X11 device
manager.

This is a leftover from when GskTexture was moved
to gdk.

Mir is in the process of switching over to the Wayland protocol,
so we don't need to maintain a separate backend, going forward.

There were still references to recent chooser and tool palette
types in the docs.

This function does bad things, and is not an
API that we want to take into GTK+ 4.

If this is a problem, it needs to be handled explicitly.

If this is a problem, it needs to be handled explicitly.

On non-windows, this doesn't do anything anyway.

Avoid the ugly priv->tool_box==NULL check in ::add (and ::remove) by
just not using template xml for this small class. Also, make sure the
GtkBin child is properly set and implement remove to also properly
remove it. Remove the manual widget margins and add some CSS for it.
Also switch to simply using a GtkCenterBox.

Since the GtkSearchBar is not the direct parent, we need to remove them
properly from priv->box_center.

both box_left and box_right are unused.

and the build.

This together with the optimizations in GtkSnapshot was causing circular
buttons to become squared when partially scrolled out of view.

We only use the widget pointer here once.

Get rid of the manual y flipping and cairo business. This keeps the gl
unit tests working at least.

This happens when deserializing testcases and it really confuses
valgrind into thinking we're longjmp()ing.

And deserializing rendernodes is slow anyway, so who cares about a few
more malloc()s.

According to meson it's the only private header that doesn't conform to
the *private.h naming.

Fix that.

GdkContentFormatsBuilder is currently not introspectable, as it does not
have a GType. We can turn it into a boxed type, but we need to implement
memory management for it.

The current gdk_content_formats_builder_free() function returns a newly
constructed value, so we cannot use it as a GBoxedFreeFunc; additionally
copying a GdkContentFormatsBuilder contents would make it a bit odd, as
you could get multiple identical GdkContentFormats out of the copies.

A simple approach is to model the GdkContentFormatsBuilder API to follow
the GBytes one: use reference counting for memory management, and have
a function to release a reference, return a GdkContentFormats, and reset
the GdkContentFormatsBuilder state.

For language bindings, we can provide a get_formats() function that
returns the GdkContentFormats instance and resets the builder instance,
leaving the reference count untouched.

For C convenience we can keep gdk_content_formats_builder_free(), and
make it a wrapper around gdk_content_formats_builder_get_formats(), with
the guarantee that it'll free the builder instance regardless of its
current reference count.

https://bugzilla.gnome.org/show_bug.cgi?id=793097
https://blogs.gnome.org/otte/2018/02/03/builders/

This makes multiple consecutive render_texture calls on the same
renderer work.

No need to check for the event type here.

As discussed.

The result won't be visible anyway. This also prevents problems with
widgets that create some resource the size of the widget, like
GtkGLArea. It also keeps us from snapshotting revealers with
size 0.

Otherwise the we fail to set the drag source icon name later on.

Now that we don't use them anywhere, it's time for them to go.

https://bugzilla.gnome.org/show_bug.cgi?id=793124

GDK has a lock to mark critical sections inside the backends.
Additionally, code that would re-enter into the GTK main loop was
supposed to hold the lock.

Back in the Good Old Days™ this was guaranteed to kind of work only on
the X11 backend, and would cause a neat explosion on any other GDK
backend.

During GTK+ 3.x we deprecated the API to enter and leave the critical
sections, and now we can remove all the internal uses of the lock, since
external API that uses GTK+ 4.x won't be able to hold the GDK lock.

https://bugzilla.gnome.org/show_bug.cgi?id=793124