tauri-apps/archived-gir-files
1
0
Fork 0
mirror of https://github.com/tauri-apps/gir-files.git synced 2026-01-31 00:45:15 +01:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #69 from bilelmoussaoui/gtk4-update

Browse Source 
gtk4: re-update
This commit is contained in:
Sebastian Dröge
2020-12-11 19:46:47 +02:00
committed by GitHub
parent 1e732a69f5 244b0e04a8
commit 071f41faec
5 changed files with 59 additions and 43 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
Gdk-4.0.gir
View File

@@ -10,7 +10,7 @@ and/or use gtk-doc annotations. -->
<include name="cairo" version="1.0"/>
<package name="gtk4"/>
<c:include name="gdk/gdk.h"/>
<namespace name="Gdk" version="4.0" shared-library="libgtk-4.so.0" c:identifier-prefixes="Gdk" c:symbol-prefixes="gdk">
<namespace name="Gdk" version="4.0" shared-library="libgtk-4.so.1" c:identifier-prefixes="Gdk" c:symbol-prefixes="gdk">
<constant name="ACTION_ALL" value="7" c:type="GDK_ACTION_ALL">
<doc xml:space="preserve">Defines all possible DND actions. This can be used in gdk_drop_status()
messages when any drop can be accepted or a more specific drop method

2
GdkWayland-4.0.gir
View File

@@ -6,7 +6,7 @@ and/or use gtk-doc annotations. -->
<include name="Gdk" version="4.0"/>
<package name="gtk4-wayland"/>
<c:include name="gdk/wayland/gdkwayland.h"/>
<namespace name="GdkWayland" version="4.0" shared-library="libgtk-4.so.0" c:identifier-prefixes="Gdk" c:symbol-prefixes="gdk">
<namespace name="GdkWayland" version="4.0" shared-library="libgtk-4.so.1" c:identifier-prefixes="Gdk" c:symbol-prefixes="gdk">
<function-macro name="IS_WAYLAND_DEVICE" c:identifier="GDK_IS_WAYLAND_DEVICE" introspectable="0">
<parameters>

2
GdkX11-4.0.gir
View File

@@ -7,7 +7,7 @@ and/or use gtk-doc annotations. -->
<include name="xlib" version="2.0"/>
<package name="gtk4-x11"/>
<c:include name="gdk/x11/gdkx.h"/>
<namespace name="GdkX11" version="4.0" shared-library="libgtk-4.so.0" c:identifier-prefixes="Gdk" c:symbol-prefixes="gdk">
<namespace name="GdkX11" version="4.0" shared-library="libgtk-4.so.1" c:identifier-prefixes="Gdk" c:symbol-prefixes="gdk">
<function-macro name="DISPLAY_XDISPLAY" c:identifier="GDK_DISPLAY_XDISPLAY" introspectable="0">
<doc xml:space="preserve">Returns the display of a #GdkDisplay.</doc>

2
Gsk-4.0.gir
View File

@@ -6,7 +6,7 @@ and/or use gtk-doc annotations. -->
<include name="Gdk" version="4.0"/>
<package name="gtk4"/>
<c:include name="gsk/gsk.h"/>
<namespace name="Gsk" version="4.0" shared-library="libgtk-4.so.0" c:identifier-prefixes="Gsk" c:symbol-prefixes="gsk">
<namespace name="Gsk" version="4.0" shared-library="libgtk-4.so.1" c:identifier-prefixes="Gsk" c:symbol-prefixes="gsk">
<function-macro name="BROADWAY_RENDERER" c:identifier="GSK_BROADWAY_RENDERER" introspectable="0">
<parameters>

94
Gtk-4.0.gir
View File

@@ -7,7 +7,7 @@ and/or use gtk-doc annotations. -->
<include name="Gsk" version="4.0"/>
<package name="gtk4"/>
<c:include name="gtk/gtk.h"/>
<namespace name="Gtk" version="4.0" shared-library="libgtk-4.so.0" c:identifier-prefixes="Gtk" c:symbol-prefixes="gtk">
<namespace name="Gtk" version="4.0" shared-library="libgtk-4.so.1" c:identifier-prefixes="Gtk" c:symbol-prefixes="gtk">
<alias name="Allocation" c:type="GtkAllocation">
<doc xml:space="preserve">A #GtkAllocation-struct of a widget represents region
which has been allocated to the widget by its parent. It is a subregion
@@ -103456,15 +103456,15 @@ titlebars.</doc>
</parameters>
</method>
<method name="fullscreen" c:identifier="gtk_window_fullscreen">
<doc xml:space="preserve">Asks to place @window in the fullscreen state. Note that you
shouldn&#x2019;t assume the window is definitely full screen afterward,
because other entities (e.g. the user or
[window manager][gtk-X11-arch]) could unfullscreen it
again, and not all window managers honor requests to fullscreen
windows. But normally the window will end up fullscreen. Just
don&#x2019;t write code that crashes if not.
<doc xml:space="preserve">Asks to place @window in the fullscreen state.
You can track iconification via the #GdkToplevel:state property</doc>
Note that you shouldn&#x2019;t assume the window is definitely full screen afterward,
because other entities (e.g. the user or [window manager][gtk-X11-arch]) could
unfullscreen it again, and not all window managers honor requests to fullscreen
windows.
You can track the result of this operation via the #GdkToplevel:state property,
or by listening to notifications of the #GtkWindow:fullscreen property.</doc>
<return-value transfer-ownership="none">
<type name="none" c:type="void"/>
@@ -103477,10 +103477,15 @@ You can track iconification via the #GdkToplevel:state property</doc>
</parameters>
</method>
<method name="fullscreen_on_monitor" c:identifier="gtk_window_fullscreen_on_monitor">
<doc xml:space="preserve">Asks to place @window in the fullscreen state. Note that you shouldn't assume
the window is definitely full screen afterward.
<doc xml:space="preserve">Asks to place @window in the fullscreen state on the given @monitor.
You can track iconification via the #GdkToplevel:state property</doc>
Note that you shouldn't assume the window is definitely full screen
afterward, or that the windowing system allows fullscreen windows on
any given monitor.
You can track the result of this operation via the #GdkToplevel:state
property, or by listening to notifications of the #GtkWindow:fullscreen
property.</doc>
<return-value transfer-ownership="none">
<type name="none" c:type="void"/>
@@ -103860,17 +103865,14 @@ initial requested state is maximized.</doc>
</parameters>
</method>
<method name="maximize" c:identifier="gtk_window_maximize">
<doc xml:space="preserve">Asks to maximize @window, so that it becomes full-screen. Note that
you shouldn&#x2019;t assume the window is definitely maximized afterward,
because other entities (e.g. the user or
[window manager][gtk-X11-arch]) could unmaximize it
again, and not all window managers support maximization. But
normally the window will end up maximized. Just don&#x2019;t write code
that crashes if not.
<doc xml:space="preserve">Asks to maximize @window, so that it fills the screen.
It&#x2019;s permitted to call this function before showing a window,
in which case the window will be maximized when it appears onscreen
initially.
Note that you shouldn&#x2019;t assume the window is definitely maximized afterward,
because other entities (e.g. the user or [window manager][gtk-X11-arch])
could unmaximize it again, and not all window managers support maximization.
It&#x2019;s permitted to call this function before showing a window, in which case
the window will be maximized when it appears onscreen initially.
You can track the result of this operation via the #GdkToplevel:state
property, or by listening to notifications on the #GtkWindow:maximized
@@ -104280,8 +104282,9 @@ will then disallow lowering the dialog below the parent.</doc>
</parameters>
</method>
<method name="set_resizable" c:identifier="gtk_window_set_resizable">
<doc xml:space="preserve">Sets whether the user can resize a window. Windows are user resizable
by default.</doc>
<doc xml:space="preserve">Sets whether the user can resize a window.
Windows are user resizable by default.</doc>
<return-value transfer-ownership="none">
<type name="none" c:type="void"/>
@@ -104405,15 +104408,17 @@ much as the window manager would have done on X.</doc>
</parameters>
</method>
<method name="unfullscreen" c:identifier="gtk_window_unfullscreen">
<doc xml:space="preserve">Asks to toggle off the fullscreen state for @window. Note that you
shouldn&#x2019;t assume the window is definitely not full screen
afterward, because other entities (e.g. the user or
[window manager][gtk-X11-arch]) could fullscreen it
again, and not all window managers honor requests to unfullscreen
windows. But normally the window will end up restored to its normal
state. Just don&#x2019;t write code that crashes if not.
<doc xml:space="preserve">Asks to remove the fullscreen state for @window, and return to its previous
state.
You can track iconification via the #GdkToplevel:state property</doc>
Note that you shouldn&#x2019;t assume the window is definitely not full screen afterward,
because other entities (e.g. the user or [window manager][gtk-X11-arch]) could
fullscreen it again, and not all window managers honor requests to unfullscreen
windows; normally the window will end up restored to its normal state. Just don&#x2019;t
write code that crashes if not.
You can track the result of this operation via the #GdkToplevel:state property,
or by listening to notifications of the #GtkWindow:fullscreen property.</doc>
<return-value transfer-ownership="none">
<type name="none" c:type="void"/>
@@ -104426,12 +104431,11 @@ You can track iconification via the #GdkToplevel:state property</doc>
</parameters>
</method>
<method name="unmaximize" c:identifier="gtk_window_unmaximize">
<doc xml:space="preserve">Asks to unmaximize @window. Note that you shouldn&#x2019;t assume the
window is definitely unmaximized afterward, because other entities
(e.g. the user or [window manager][gtk-X11-arch])
could maximize it again, and not all window
managers honor requests to unmaximize. But normally the window will
end up unmaximized. Just don&#x2019;t write code that crashes if not.
<doc xml:space="preserve">Asks to unmaximize @window.
Note that you shouldn&#x2019;t assume the window is definitely unmaximized afterward,
because other entities (e.g. the user or [window manager][gtk-X11-arch]) could
maximize it again, and not all window managers honor requests to unmaximize.
You can track the result of this operation via the #GdkToplevel:state
property, or by listening to notifications on the #GtkWindow:maximized
@@ -104517,7 +104521,13 @@ and should not be set by applications.</doc>
<property name="focus-widget" writable="1" transfer-ownership="none">
<type name="Widget"/>
</property>
<property name="fullscreen" writable="1" construct="1" transfer-ownership="none">
<property name="fullscreened" writable="1" construct="1" transfer-ownership="none">
<doc xml:space="preserve">Whether the window is fullscreen.
Setting this property is the equivalent of calling gtk_window_fullscreen()
and gtk_window_unfullscreen(); either operation is asynchronous, which
means you will need to connect to the #GObject::notify signal in order to
know whether the operation was successful.</doc>
<type name="gboolean" c:type="gboolean"/>
</property>
<property name="hide-on-close" writable="1" transfer-ownership="none">
@@ -104532,6 +104542,12 @@ use as the window icon. See #GtkIconTheme for more details.</doc>
<type name="gboolean" c:type="gboolean"/>
</property>
<property name="maximized" writable="1" construct="1" transfer-ownership="none">
<doc xml:space="preserve">Whether the window is maximized.
Setting this property is the equivalent of calling gtk_window_maximize()
and gtk_window_unmaximize(); either operation is asynchronous, which
means you will need to connect to the #GObject::notify signal in order to
know whether the operation was successful.</doc>
<type name="gboolean" c:type="gboolean"/>
</property>
<property name="mnemonics-visible" writable="1" transfer-ownership="none">