Update GIR files

Author: bilelmoussaoui

GLib-2.0.gir

@@ -27333,6 +27333,24 @@ destroying it will effectively unset the callback similar to calling
           </instance-parameter>
         </parameters>
       </method>
+      <method name="dup_context" c:identifier="g_source_dup_context" version="2.86">
+        <doc xml:space="preserve">Gets the [struct@GLib.MainContext] with which the source is associated.
+
+You can call this on a source that has been destroyed. You can
+always call this function on the source returned from
+[func@GLib.main_current_source].</doc>
+        <return-value transfer-ownership="full" nullable="1">
+          <doc xml:space="preserve">the [struct@GLib.MainContext] with which the
+              source is associated, or `NULL`.</doc>
+          <type name="MainContext" c:type="GMainContext*"/>
+        </return-value>
+        <parameters>
+          <instance-parameter name="source" transfer-ownership="none">
+            <doc xml:space="preserve">a #GSource</doc>
+            <type name="Source" c:type="GSource*"/>
+          </instance-parameter>
+        </parameters>
+      </method>
       <method name="get_can_recurse" c:identifier="g_source_get_can_recurse">
         <doc xml:space="preserve">Checks whether a source is allowed to be called recursively.
 see [method@GLib.Source.set_can_recurse].</doc>
@@ -27355,7 +27373,11 @@ that the [struct@GLib.MainContext] it was attached to still exists (in which
 case it will return that [struct@GLib.MainContext]). In particular, you can
 always call this function on the source returned from
 [func@GLib.main_current_source]. But calling this function on a source
-whose [struct@GLib.MainContext] has been destroyed is an error.</doc>
+whose [struct@GLib.MainContext] has been destroyed is an error.
+
+If the associated [struct@GLib.MainContext] could be destroy concurrently from
+a different thread, then this function is not safe to call and
+[method@GLib.Source.dup_context] should be used instead.</doc>
         <return-value transfer-ownership="none" nullable="1">
           <doc xml:space="preserve">the #GMainContext with which the
               source is associated, or %NULL if the context has not

GObject-2.0.gir

@@ -7340,14 +7340,7 @@ should not destroy the object in the normal way.</doc>
         <doc xml:space="preserve">Releases all references to other objects. This can be used to break
 reference cycles.
 
-This function should only be called from object system implementations.
-
-This function temporarily acquires another strong reference while running
-dispose.
-
-This first clears all #GWeakRef pointers and then calls
-#GObjectClass.dispose. (Before 2.86, #GWeakRef pointers were
-cleared after #GObjectClass.dispose).</doc>
+This function should only be called from object system implementations.</doc>
         <return-value transfer-ownership="none">
           <type name="none" c:type="void"/>
         </return-value>
@@ -14402,19 +14395,15 @@ reference is thread-safe: converting a weak pointer to a reference is
 atomic with respect to invalidation of weak pointers to destroyed
 objects.
 
-#GWeakRefs are reset before calling #GObjectClass.dispose.
 If the object's #GObjectClass.dispose method results in additional
 references to the object being held (&#x2018;re-referencing&#x2019;), any #GWeakRefs taken
-before it was disposed will continue to point to %NULL. If during disposal
-the object gets re-referenced and resurrected, the #GWeakRefs taken during
-disposal will be set until the reference count drops towards zero again and
-#GObjectClass.dispose is called again. If #GWeakRefs were taken during
-disposal but the object not resurrected, they will be set to %NULL right
-after, before finalization.
-
-Note that #GObjectClass.run_dispose() also resets #GWeakRefs. As such, the
-#GWeakRef actually tracks whether #GObjectClass.dispose() was called
-and not the reference count reaching zero.</doc>
+before it was disposed will continue to point to %NULL.  Any #GWeakRefs taken
+during disposal and after re-referencing, or after disposal has returned due
+to the re-referencing, will continue to point to the object until its refcount
+goes back to zero, at which point they too will be invalidated.
+
+It is invalid to take a #GWeakRef on an object during #GObjectClass.dispose
+without first having or creating a strong reference to the object.</doc>
       <union name="priv" c:type="priv">
         <field name="p" writable="1">
           <type name="gpointer" c:type="gpointer"/>

Gdk-4.0.gir

@@ -1173,6 +1173,26 @@ color states will never compare equal.</doc>
           </parameter>
         </parameters>
       </method>
+      <method name="equivalent" c:identifier="gdk_color_state_equivalent" version="4.20">
+        <doc xml:space="preserve">Compares two `GdkColorStates` for equivalence.
+
+Two objects that represent the same color state should be equivalent,
+even though they may not be equal in the sense of [method@Gdk.ColorState.equal].</doc>
+        <return-value transfer-ownership="none">
+          <doc xml:space="preserve">%TRUE if the two color states are equivalent</doc>
+          <type name="gboolean" c:type="gboolean"/>
+        </return-value>
+        <parameters>
+          <instance-parameter name="self" transfer-ownership="none">
+            <doc xml:space="preserve">a `GdkColorState`</doc>
+            <type name="ColorState" c:type="GdkColorState*"/>
+          </instance-parameter>
+          <parameter name="other" transfer-ownership="none">
+            <doc xml:space="preserve">another `GdkColorStatee`</doc>
+            <type name="ColorState" c:type="GdkColorState*"/>
+          </parameter>
+        </parameters>
+      </method>
       <method name="ref" c:identifier="gdk_color_state_ref" version="4.16">
         <doc xml:space="preserve">Increase the reference count of @self.</doc>
         <return-value transfer-ownership="full">
@@ -6860,7 +6880,10 @@ If the last reference is dropped, the structure is freed.</doc>
         <doc xml:space="preserve">A touchpad hold gesture event, the current state is determined by its phase
 field.</doc>
       </member>
-      <member name="event_last" value="29" c:identifier="GDK_EVENT_LAST" glib:nick="event-last" glib:name="GDK_EVENT_LAST">
+      <member name="pad_dial" value="29" c:identifier="GDK_PAD_DIAL" glib:nick="pad-dial" glib:name="GDK_PAD_DIAL">
+        <doc xml:space="preserve">A tablet pad axis event from a "dial".</doc>
+      </member>
+      <member name="event_last" value="30" c:identifier="GDK_EVENT_LAST" glib:nick="event-last" glib:name="GDK_EVENT_LAST">
         <doc xml:space="preserve">marks the end of the GdkEventType enumeration.</doc>
       </member>
     </enumeration>
@@ -20092,12 +20115,14 @@ data.</doc>
       <implements name="Paintable"/>
       <implements name="Gio.Icon"/>
       <implements name="Gio.LoadableIcon"/>
-      <constructor name="new_for_pixbuf" c:identifier="gdk_texture_new_for_pixbuf">
+      <constructor name="new_for_pixbuf" c:identifier="gdk_texture_new_for_pixbuf" deprecated="1" deprecated-version="4.20">
         <doc xml:space="preserve">Creates a new texture object representing the `GdkPixbuf`.
 
 This function is threadsafe, so that you can e.g. use GTask
-and [method@Gio.Task.run_in_thread] to avoid blocking the main thread
-while loading a big image.</doc>
+and [method@Gio.Task.run_in_thread] to avoid blocking the main
+thread while loading a big image.</doc>
+        <doc-deprecated xml:space="preserve">Use e.g. libglycin, which can load many image
+  formats into a `GdkTexture`</doc-deprecated>
         <return-value transfer-ownership="full">
           <doc xml:space="preserve">a new `GdkTexture`</doc>
           <type name="Texture" c:type="GdkTexture*"/>
@@ -20115,6 +20140,10 @@ while loading a big image.</doc>
 The file format is detected automatically. The supported formats
 are PNG, JPEG and TIFF, though more formats might be available.
 
+Note that this function should not be used with untrusted data.
+Use a proper image loading framework such as libglycin, which can
+load many image formats into a `GdkTexture`.
+
 If %NULL is returned, then @error will be set.
 
 This function is threadsafe, so that you can e.g. use GTask
@@ -20137,6 +20166,10 @@ while loading a big image.</doc>
 The file format is detected automatically. The supported formats
 are PNG, JPEG and TIFF, though more formats might be available.
 
+Note that this function should not be used with untrusted data.
+Use a proper image loading framework such as libglycin, which can
+load many image formats into a `GdkTexture`.
+
 If %NULL is returned, then @error will be set.
 
 This function is threadsafe, so that you can e.g. use GTask
@@ -20159,6 +20192,10 @@ while loading a big image.</doc>
 The file format is detected automatically. The supported formats
 are PNG, JPEG and TIFF, though more formats might be available.
 
+Note that this function should not be used with untrusted data.
+Use a proper image loading framework such as libglycin, which can
+load many image formats into a `GdkTexture`.
+
 If %NULL is returned, then @error will be set.
 
 This function is threadsafe, so that you can e.g. use GTask
@@ -20179,7 +20216,7 @@ while loading a big image.</doc>
         <doc xml:space="preserve">Creates a new texture by loading an image from a resource.
 
 The file format is detected automatically. The supported formats
-are PNG and JPEG, though more formats might be available.
+are PNG, JPEG and TIFF, though more formats might be available.
 
 It is a fatal error if @resource_path does not specify a valid
 image resource and the program will abort if that happens.
@@ -20309,9 +20346,9 @@ downloading the texture.</doc>
 
 This is a utility function intended for debugging and testing.
 If you want more control over formats, proper error handling or
-want to store to a [iface@Gio.File] or other location, you might want to
-use [method@Gdk.Texture.save_to_png_bytes] or look into the
-gdk-pixbuf library.</doc>
+want to store to a [iface@Gio.File] or other location, you might
+want to use [method@Gdk.Texture.save_to_png_bytes] or look into
+the libglycin library.</doc>
         <return-value transfer-ownership="none">
           <doc xml:space="preserve">%TRUE if saving succeeded, %FALSE on failure.</doc>
           <type name="gboolean" c:type="gboolean"/>
@@ -20337,7 +20374,7 @@ portable way to do that.
 
 If you need more control over the generated image, such as
 attaching metadata, you should look into an image handling
-library such as the gdk-pixbuf library.
+library such as the libglycin library.
 
 If you are dealing with high dynamic range float data, you
 might also want to consider [method@Gdk.Texture.save_to_tiff_bytes]
@@ -21952,11 +21989,12 @@ set with cairo_surface_set_device_offset().</doc>
         </parameter>
       </parameters>
     </function>
-    <function name="cairo_set_source_pixbuf" c:identifier="gdk_cairo_set_source_pixbuf">
+    <function name="cairo_set_source_pixbuf" c:identifier="gdk_cairo_set_source_pixbuf" deprecated="1" deprecated-version="4.20">
       <doc xml:space="preserve">Sets the given pixbuf as the source pattern for @cr.
 
 The pattern has an extend mode of %CAIRO_EXTEND_NONE and is aligned
 so that the origin of @pixbuf is @pixbuf_x, @pixbuf_y.</doc>
+      <doc-deprecated xml:space="preserve">Use cairo_set_source_surface() and gdk_texture_download()</doc-deprecated>
       <return-value transfer-ownership="none">
         <type name="none" c:type="void"/>
       </return-value>
@@ -22152,7 +22190,11 @@ is returned.</doc>
       </parameters>
     </function>
     <function name="content_register_deserializer" c:identifier="gdk_content_register_deserializer">
-      <doc xml:space="preserve">Registers a function to deserialize object of a given type.</doc>
+      <doc xml:space="preserve">Registers a function to deserialize object of a given type.
+
+Since 4.20, when looking up a deserializer to use, GTK will
+use the last registered deserializer for a given mime type,
+so applications can override the built-in deserializers.</doc>
       <return-value transfer-ownership="none">
         <type name="none" c:type="void"/>
       </return-value>
@@ -22180,7 +22222,11 @@ is returned.</doc>
       </parameters>
     </function>
     <function name="content_register_serializer" c:identifier="gdk_content_register_serializer">
-      <doc xml:space="preserve">Registers a function to serialize objects of a given type.</doc>
+      <doc xml:space="preserve">Registers a function to serialize objects of a given type.
+
+Since 4.20, when looking up a serializer to use, GTK will
+use the last registered serializer for a given mime type,
+so applications can override the built-in serializers.</doc>
       <return-value transfer-ownership="none">
         <type name="none" c:type="void"/>
       </return-value>

GdkWayland-4.0.gir

@@ -510,6 +510,20 @@ and thus may require changes in the future.</doc>
           </parameter>
         </parameters>
       </method>
+      <method name="get_xdg_toplevel" c:identifier="gdk_wayland_toplevel_get_xdg_toplevel" version="4.20">
+        <doc xml:space="preserve">Returns the Wayland `xdg_toplevel` of a toplevel,
+if it has one.</doc>
+        <return-value transfer-ownership="none" nullable="1">
+          <doc xml:space="preserve">a Wayland `xdg_toplevel`</doc>
+          <type name="gpointer" c:type="xdg_toplevel*"/>
+        </return-value>
+        <parameters>
+          <instance-parameter name="toplevel" transfer-ownership="none">
+            <doc xml:space="preserve">a toplevel</doc>
+            <type name="WaylandToplevel" c:type="GdkToplevel*"/>
+          </instance-parameter>
+        </parameters>
+      </method>
       <method name="set_application_id" c:identifier="gdk_wayland_toplevel_set_application_id">
         <doc xml:space="preserve">Sets the application id on a `GdkToplevel`.</doc>
         <return-value transfer-ownership="none">