Memory-managed wrapper type.

Type class for types which can be safely cast to Window, for instance with toWindow.

Cast to Window, for types for which this is known to be safe. For general casts, use castTo.

A convenience alias for Nothing :: Maybe Window.

Activates the default widget for the window, unless the current focused widget has been configured to receive the default action (see widgetSetReceivesDefault), in which case the focused widget is activated.

Activates the current focused widget within the window.

Activates mnemonics and accelerators for this Window. This is normally called by the default ::key_press_event handler for toplevel windows, however in some cases it may be useful to call this directly when overriding the standard key handling for a toplevel window.

Since: 2.4

Associate accelGroup with window, such that calling accelGroupsActivate on window will activate accelerators in accelGroup.

Adds a mnemonic to this window.

Starts moving a window. This function is used if an application has window movement grips. When GDK can support it, the window movement will be done using the standard mechanism for the [window manager][gtk-X11-arch] or windowing system. Otherwise, GDK will try to emulate window movement, potentially not all that well, depending on the windowing system.

Starts resizing a window. This function is used if an application has window resizing controls. When GDK can support it, the resize will be done using the standard mechanism for the [window manager][gtk-X11-arch] or windowing system. Otherwise, GDK will try to emulate window resizing, potentially not all that well, depending on the windowing system.

Requests that the window is closed, similar to what happens when a window manager close button is clicked.

This function can be used with close buttons in custom titlebars.

Since: 3.10

Asks to deiconify (i.e. unminimize) the specified window. Note that you shouldn’t assume the window is definitely deiconified afterward, because other entities (e.g. the user or [window manager][gtk-X11-arch])) could iconify it again before your code which assumes deiconification gets to run.

You can track iconification via the “window-state-event” signal on Widget.

Asks to place window in the fullscreen state. Note that you shouldn’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’t write code that crashes if not.

You can track the fullscreen state via the “window-state-event” signal on Widget.

Since: 2.2

Asks to place window in the fullscreen state. Note that you shouldn't assume the window is definitely full screen afterward.

You can track the fullscreen state via the "window-state-event" signal on Widget.

Since: 3.18

Gets the value set by windowSetAcceptFocus.

Since: 2.4

Gets the Application associated with the window (if any).

Since: 3.0

Fetches the attach widget for this window. See windowSetAttachedTo.

Since: 3.4

Returns whether the window has been set to have decorations such as a title bar via windowSetDecorated.

Gets the value set by windowSetDefaultIconList. The list is a copy and should be freed with g_list_free(), but the pixbufs in the list have not had their reference count incremented.

Returns the fallback icon name for windows that has been set with windowSetDefaultIconName. The returned string is owned by GTK+ and should not be modified. It is only valid until the next call to windowSetDefaultIconName.

Since: 2.16

Gets the default size of the window. A value of -1 for the width or height indicates that a default size has not been explicitly set for that dimension, so the “natural” size of the window will be used.

Returns the default widget for window. See windowSetDefault for more details.

Since: 2.14

Returns whether the window has been set to have a close button via windowSetDeletable.

Since: 2.10

Returns whether the window will be destroyed with its transient parent. See gtk_window_set_destroy_with_parent ().

Retrieves the current focused widget within the window. Note that this is the widget that would have the focus if the toplevel window focused; if the toplevel window is not focused then gtk_widget_has_focus (widget) will not be True for the widget.

Gets the value set by windowSetFocusOnMap.

Since: 2.6

Gets the value of the Window:focus-visible property.

Since: 3.2

Gets the value set by windowSetGravity.

Returns the group for window or the default group, if window is Nothing or if window does not have an explicit window group.

Since: 2.10

Determines whether the window may have a resize grip.

Since: 3.0

Returns whether the window has requested to have its titlebar hidden when maximized. See gtk_window_set_hide_titlebar_when_maximized ().

Since: 3.4

Gets the value set by windowSetIcon (or if you've called windowSetIconList, gets the first icon in the icon list).

Retrieves the list of icons set by windowSetIconList. The list is copied, but the reference count on each member won’t be incremented.

Returns the name of the themed icon for the window, see windowSetIconName.

Since: 2.6

Returns the mnemonic modifier for this window. See windowSetMnemonicModifier.

Gets the value of the Window:mnemonics-visible property.

Since: 2.20

Returns whether the window is modal. See windowSetModal.

Fetches the requested opacity for this window. See windowSetOpacity.

Since: 2.12

This function returns the position you need to pass to windowMove to keep window in its current position. This means that the meaning of the returned value varies with window gravity. See windowMove for more details.

The reliability of this function depends on the windowing system currently in use. Some windowing systems, such as Wayland, do not support a global coordinate system, and thus the position of the window will always be (0, 0). Others, like X11, do not have a reliable way to obtain the geometry of the decorations of a window if they are provided by the window manager. Additionally, on X11, window manager have been known to mismanage window gravity, which result in windows moving even if you use the coordinates of the current position as returned by this function.

If you haven’t changed the window gravity, its gravity will be GDK_GRAVITY_NORTH_WEST. This means that windowGetPosition gets the position of the top-left corner of the window manager frame for the window. windowMove sets the position of this same top-left corner.

If a window has gravity GDK_GRAVITY_STATIC the window manager frame is not relevant, and thus windowGetPosition will always produce accurate results. However you can’t use static gravity to do things like place a window in a corner of the screen, because static gravity ignores the window manager decorations.

Ideally, this function should return appropriate values if the window has client side decorations, assuming that the windowing system supports global coordinates.

In practice, saving the window position should not be left to applications, as they lack enough knowledge of the windowing system and the window manager state to effectively do so. The appropriate way to implement saving the window position is to use a platform-specific protocol, wherever that is available.

Gets the value set by windowSetResizable.

If a window has a resize grip, this will retrieve the grip position, width and height into the specified Rectangle.

Since: 3.0

Returns the role of the window. See windowSetRole for further explanation.

Returns the Screen associated with window.

Since: 2.2

Obtains the current size of window.

If window is not visible on screen, this function return the size GTK+ will suggest to the [window manager][gtk-X11-arch] for the initial window size (but this is not reliably the same as the size the window manager will actually select). See: windowSetDefaultSize.

Depending on the windowing system and the window manager constraints, the size returned by this function may not match the size set using windowResize; additionally, since windowResize may be implemented as an asynchronous operation, GTK+ cannot guarantee in any way that this code:

C code

 // width and height are set elsewhere
 gtk_window_resize (window, width, height);

 int new_width, new_height;
 gtk_window_get_size (window, &new_width, &new_height);

will result in new_width and new_height matching width and height, respectively.

This function will return the logical size of the Window, excluding the widgets used in client side decorations; there is, however, no guarantee that the result will be completely accurate because client side decoration may include widgets that depend on the user preferences and that may not be visibile at the time you call this function.

The dimensions returned by this function are suitable for being stored across sessions; use windowSetDefaultSize to restore them when before showing the window.

To avoid potential race conditions, you should only call this function in response to a size change notification, for instance inside a handler for the Widget::size-allocate signal, or inside a handler for the Widget::configure-event signal:

C code

static void
on_size_allocate (GtkWidget *widget, GtkAllocation *allocation)
{
  int new_width, new_height;

  gtk_window_get_size (GTK_WINDOW (widget), &new_width, &new_height);

  ...
}

Note that, if you connect to the Widget::size-allocate signal, you should not use the dimensions of the GtkAllocation passed to the signal handler, as the allocation may contain client side decorations added by GTK+, depending on the windowing system in use.

If you are getting a window size in order to position the window on the screen, you should, instead, simply set the window’s semantic type with windowSetTypeHint, which allows the window manager to e.g. center dialogs. Also, if you set the transient parent of dialogs with windowSetTransientFor window managers will often center the dialog over its parent window. It's much preferred to let the window manager handle these cases rather than doing it yourself, because all apps will behave consistently and according to user or system preferences, if the window manager handles it. Also, the window manager can take into account the size of the window decorations and border that it may add, and of which GTK+ has no knowledge. Additionally, positioning windows in global screen coordinates may not be allowed by the windowing system. For more information, see: windowSetPosition.

Gets the value set by windowSetSkipPagerHint.

Since: 2.2

Gets the value set by windowSetSkipTaskbarHint

Since: 2.2

Retrieves the title of the window. See windowSetTitle.

Returns the custom titlebar that has been set with windowSetTitlebar.

Since: 3.16

Fetches the transient parent for this window. See windowSetTransientFor.

Gets the type hint for this window. See windowSetTypeHint.

Gets the value set by windowSetUrgencyHint

Since: 2.8

Gets the type of the window. See WindowType.

Since: 2.20

Returns whether window has an explicit window group.

Returns whether the input focus is within this GtkWindow. For real toplevel windows, this is identical to windowIsActive, but for embedded windows, like Plug, the results will differ.

Since: 2.4

Asks to iconify (i.e. minimize) the specified window. Note that you shouldn’t assume the window is definitely iconified afterward, because other entities (e.g. the user or [window manager][gtk-X11-arch]) could deiconify it again, or there may not be a window manager in which case iconification isn’t possible, etc. But normally the window will end up iconified. Just don’t write code that crashes if not.

It’s permitted to call this function before showing a window, in which case the window will be iconified before it ever appears onscreen.

You can track iconification via the “window-state-event” signal on Widget.

Returns whether the window is part of the current active toplevel. (That is, the toplevel window receiving keystrokes.) The return value is True if the window is active toplevel itself, but also if it is, say, a Plug embedded in the active toplevel. You might use this function if you wanted to draw a widget differently in an active window from a widget in an inactive window. See windowHasToplevelFocus

Since: 2.4

Retrieves the current maximized state of window.

Note that since maximization is ultimately handled by the window manager and happens asynchronously to an application request, you shouldn’t assume the return value of this function changing immediately (or at all), as an effect of calling windowMaximize or windowUnmaximize.

Since: 3.12

Returns a list of all existing toplevel windows. The widgets in the list are not individually referenced. If you want to iterate through the list and perform actions involving callbacks that might destroy the widgets, you must call g_list_foreach (result, (GFunc)g_object_ref, NULL) first, and then unref all the widgets afterwards.

Asks to maximize window, so that it becomes full-screen. Note that you shouldn’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’t write code that crashes if not.

It’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 maximization via the “window-state-event” signal on Widget, or by listening to notifications on the Window:is-maximized property.

Activates the targets associated with the mnemonic.

Asks the [window manager][gtk-X11-arch] to move window to the given position. Window managers are free to ignore this; most window managers ignore requests for initial window positions (instead using a user-defined placement algorithm) and honor requests after the window has already been shown.

Note: the position is the position of the gravity-determined reference point for the window. The gravity determines two things: first, the location of the reference point in root window coordinates; and second, which point on the window is positioned at the reference point.

By default the gravity is GDK_GRAVITY_NORTH_WEST, so the reference point is simply the x, y supplied to windowMove. The top-left corner of the window decorations (aka window frame or border) will be placed at x, y. Therefore, to position a window at the top left of the screen, you want to use the default gravity (which is GDK_GRAVITY_NORTH_WEST) and move the window to 0,0.

To position a window at the bottom right corner of the screen, you would set GDK_GRAVITY_SOUTH_EAST, which means that the reference point is at x + the window width and y + the window height, and the bottom-right corner of the window border will be placed at that reference point. So, to place a window in the bottom right corner you would first set gravity to south east, then write: gtk_window_move (window, gdk_screen_width () - window_width, gdk_screen_height () - window_height) (note that this example does not take multi-head scenarios into account).

The Extended Window Manager Hints Specification has a nice table of gravities in the “implementation notes” section.

The windowGetPosition documentation may also be relevant.

Creates a new Window, which is a toplevel window that can contain other widgets. Nearly always, the type of the window should be GTK_WINDOW_TOPLEVEL. If you’re implementing something like a popup menu from scratch (which is a bad idea, just use Menu), you might use GTK_WINDOW_POPUP. GTK_WINDOW_POPUP is not for dialogs, though in some other toolkits dialogs are called “popups”. In GTK+, GTK_WINDOW_POPUP means a pop-up menu or pop-up tooltip. On X11, popup windows are not controlled by the [window manager][gtk-X11-arch].

If you simply want an undecorated window (no window borders), use windowSetDecorated, don’t use GTK_WINDOW_POPUP.

All top-level windows created by windowNew are stored in an internal top-level window list. This list can be obtained from windowListToplevels. Due to Gtk+ keeping a reference to the window internally, windowNew does not return a reference to the caller.

To delete a Window, call widgetDestroy.

Parses a standard X Window System geometry string - see the manual page for X (type “man X”) for details on this. windowParseGeometry does work on all GTK+ ports including Win32 but is primarily intended for an X environment.

If either a size or a position can be extracted from the geometry string, windowParseGeometry returns True and calls windowSetDefaultSize and/or windowMove to resize/move the window.

If windowParseGeometry returns True, it will also set the GDK_HINT_USER_POS and/or GDK_HINT_USER_SIZE hints indicating to the window manager that the size/position of the window was user-specified. This causes most window managers to honor the geometry.

Note that for windowParseGeometry to work as expected, it has to be called when the window has its “final” size, i.e. after calling widgetShowAll on the contents and windowSetGeometryHints on the window.

C code

#include <gtk/gtk.h>

static void
fill_with_content (GtkWidget *vbox)
{
  // fill with content...
}

int
main (int argc, char *argv[])
{
  GtkWidget *window, *vbox;
  GdkGeometry size_hints = {
    100, 50, 0, 0, 100, 50, 10,
    10, 0.0, 0.0, GDK_GRAVITY_NORTH_WEST
  };

  gtk_init (&argc, &argv);

  window = gtk_window_new (GTK_WINDOW_TOPLEVEL);
  vbox = gtk_box_new (GTK_ORIENTATION_VERTICAL, 0);

  gtk_container_add (GTK_CONTAINER (window), vbox);
  fill_with_content (vbox);
  gtk_widget_show_all (vbox);

  gtk_window_set_geometry_hints (GTK_WINDOW (window),
	  			    NULL,
				    &size_hints,
				    GDK_HINT_MIN_SIZE |
				    GDK_HINT_BASE_SIZE |
				    GDK_HINT_RESIZE_INC);

  if (argc > 1)
    {
      gboolean res;
      res = gtk_window_parse_geometry (GTK_WINDOW (window),
                                       argv[1]);
      if (! res)
        fprintf (stderr,
                 "Failed to parse “%s”\n",
                 argv[1]);
    }

  gtk_widget_show_all (window);
  gtk_main ();

  return 0;
}

Presents a window to the user. This may mean raising the window in the stacking order, deiconifying it, moving it to the current desktop, and/or giving it the keyboard focus, possibly dependent on the user’s platform, window manager, and preferences.

If window is hidden, this function calls widgetShow as well.

This function should be used when the user tries to open a window that’s already open. Say for example the preferences dialog is currently open, and the user chooses Preferences from the menu a second time; use windowPresent to move the already-open dialog where the user can see it.

If you are calling this function in response to a user interaction, it is preferable to use windowPresentWithTime.

Presents a window to the user in response to a user interaction. If you need to present a window without a timestamp, use windowPresent. See windowPresent for details.

Since: 2.8

Propagate a key press or release event to the focus widget and up the focus container chain until a widget handles event. This is normally called by the default ::key_press_event and ::key_release_event handlers for toplevel windows, however in some cases it may be useful to call this directly when overriding the standard key handling for a toplevel window.

Since: 2.4

Reverses the effects of windowAddAccelGroup.

Removes a mnemonic from this window.

Hides window, then reshows it, resetting the default size and position of the window. Used by GUI builders only.

Resizes the window as if the user had done so, obeying geometry constraints. The default geometry constraint is that windows may not be smaller than their size request; to override this constraint, call widgetSetSizeRequest to set the window's request to a smaller value.

If windowResize is called before showing a window for the first time, it overrides any default size set with windowSetDefaultSize.

Windows may not be resized smaller than 1 by 1 pixels.

When using client side decorations, GTK+ will do its best to adjust the given size so that the resulting window size matches the requested size without the title bar, borders and shadows added for the client side decorations, but there is no guarantee that the result will be totally accurate because these widgets added for client side decorations depend on the theme and may not be realized or visible at the time windowResize is issued.

If the GtkWindow has a titlebar widget (see windowSetTitlebar), then typically, windowResize will compensate for the height of the titlebar widget only if the height is known when the resulting GtkWindow configuration is issued. For example, if new widgets are added after the GtkWindow configuration and cause the titlebar widget to grow in height, this will result in a window content smaller that specified by windowResize and not a larger window.

Determines whether a resize grip is visible for the specified window.

Since: 3.0

Like windowResize, but width and height are interpreted in terms of the base size and increment set with gtk_window_set_geometry_hints.

Since: 3.0

Windows may set a hint asking the desktop environment not to receive the input focus. This function sets this hint.

Since: 2.4

Sets or unsets the Application associated with the window.

The application will be kept alive for at least as long as it has any windows associated with it (see applicationHold for a way to keep it alive without windows).

Normally, the connection between the application and the window will remain until the window is destroyed, but you can explicitly remove it by setting the application to Nothing.

This is equivalent to calling applicationRemoveWindow and/or applicationAddWindow on the old/new applications as relevant.

Since: 3.0

Marks window as attached to attachWidget. This creates a logical binding between the window and the widget it belongs to, which is used by GTK+ to propagate information such as styling or accessibility to window as if it was a children of attachWidget.

Examples of places where specifying this relation is useful are for instance a Menu created by a ComboBox, a completion popup window created by Entry or a typeahead search entry created by TreeView.

Note that this function should not be confused with windowSetTransientFor, which specifies a window manager relation between two toplevels instead.

Passing Nothing for attachWidget detaches the window.

Since: 3.4

By default, after showing the first Window, GTK+ calls notifyStartupComplete. Call this function to disable the automatic startup notification. You might do this if your first window is a splash screen, and you want to delay notification until after your real main window has been shown, for example.

In that example, you would disable startup notification temporarily, show your splash screen, then re-enable it so that showing the main window would automatically result in notification.

Since: 2.2

By default, windows are decorated with a title bar, resize controls, etc. Some [window managers][gtk-X11-arch] allow GTK+ to disable these decorations, creating a borderless window. If you set the decorated property to False using this function, GTK+ will do its best to convince the window manager not to decorate the window. Depending on the system, this function may not have any effect when called on a window that is already visible, so you should call it before calling widgetShow.

On Windows, this function always works, since there’s no window manager policy involved.

The default widget is the widget that’s activated when the user presses Enter in a dialog (for example). This function sets or unsets the default widget for a Window. When setting (rather than unsetting) the default widget it’s generally easier to call widgetGrabDefault on the widget. Before making a widget the default widget, you must call widgetSetCanDefault on the widget you’d like to make the default.

Like windowSetDefaultSize, but width and height are interpreted in terms of the base size and increment set with gtk_window_set_geometry_hints.

Since: 3.0

Sets an icon to be used as fallback for windows that haven't had windowSetIcon called on them from a pixbuf.

Since: 2.4

Sets an icon to be used as fallback for windows that haven't had windowSetIconList called on them from a file on disk. Warns on failure if err is Nothing.

Since: 2.2

Sets an icon list to be used as fallback for windows that haven't had windowSetIconList called on them to set up a window-specific icon list. This function allows you to set up the icon for all windows in your app at once.

See windowSetIconList for more details.

Sets an icon to be used as fallback for windows that haven't had windowSetIconList called on them from a named themed icon, see windowSetIconName.

Since: 2.6

Sets the default size of a window. If the window’s “natural” size (its size request) is larger than the default, the default will be ignored. More generally, if the default size does not obey the geometry hints for the window (windowSetGeometryHints can be used to set these explicitly), the default size will be clamped to the nearest permitted size.

Unlike widgetSetSizeRequest, which sets a size request for a widget and thus would keep users from shrinking the window, this function only sets the initial size, just as if the user had resized the window themselves. Users can still shrink the window again as they normally would. Setting a default size of -1 means to use the “natural” default size (the size request of the window).

For more control over a window’s initial size and how resizing works, investigate windowSetGeometryHints.

For some uses, windowResize is a more appropriate function. windowResize changes the current size of the window, rather than the size to be used on initial display. windowResize always affects the window itself, not the geometry widget.

The default size of a window only affects the first time a window is shown; if a window is hidden and re-shown, it will remember the size it had prior to hiding, rather than using the default size.

Windows can’t actually be 0x0 in size, they must be at least 1x1, but passing 0 for width and height is OK, resulting in a 1x1 default size.

If you use this function to reestablish a previously saved window size, note that the appropriate size to save is the one returned by windowGetSize. Using the window allocation directly will not work in all circumstances and can lead to growing or shrinking windows.

By default, windows have a close button in the window frame. Some [window managers][gtk-X11-arch] allow GTK+ to disable this button. If you set the deletable property to False using this function, GTK+ will do its best to convince the window manager not to show a close button. Depending on the system, this function may not have any effect when called on a window that is already visible, so you should call it before calling widgetShow.

On Windows, this function always works, since there’s no window manager policy involved.

Since: 2.10

If setting is True, then destroying the transient parent of window will also destroy window itself. This is useful for dialogs that shouldn’t persist beyond the lifetime of the main window they're associated with, for example.

If focus is not the current focus widget, and is focusable, sets it as the focus widget for the window. If focus is Nothing, unsets the focus widget for this window. To set the focus to a particular widget in the toplevel, it is usually more convenient to use widgetGrabFocus instead of this function.

Windows may set a hint asking the desktop environment not to receive the input focus when the window is mapped. This function sets this hint.

Since: 2.6

Sets the Window:focus-visible property.

Since: 3.2

This function sets up hints about how a window can be resized by the user. You can set a minimum and maximum size; allowed resize increments (e.g. for xterm, you can only resize by the size of a character); aspect ratios; and more. See the Geometry struct.

Window gravity defines the meaning of coordinates passed to windowMove. See windowMove and Gravity for more details.

The default window gravity is GDK_GRAVITY_NORTH_WEST which will typically “do what you mean.”

Sets whether window has a corner resize grip.

Note that the resize grip is only shown if the window is actually resizable and not maximized. Use windowResizeGripIsVisible to find out if the resize grip is currently shown.

Since: 3.0

Tells GTK+ whether to drop its extra reference to the window when widgetDestroy is called.

This function is only exported for the benefit of language bindings which may need to keep the window alive until their wrapper object is garbage collected. There is no justification for ever calling this function in an application.

Since: 3.0

If setting is True, then window will request that it’s titlebar should be hidden when maximized. This is useful for windows that don’t convey any information other than the application name in the titlebar, to put the available screen space to better use. If the underlying window system does not support the request, the setting will not have any effect.

Note that custom titlebars set with windowSetTitlebar are not affected by this. The application is in full control of their content and visibility anyway.

Since: 3.4

Sets up the icon representing a Window. This icon is used when the window is minimized (also known as iconified). Some window managers or desktop environments may also place it in the window frame, or display it in other contexts. On others, the icon is not used at all, so your mileage may vary.

The icon should be provided in whatever size it was naturally drawn; that is, don’t scale the image before passing it to GTK+. Scaling is postponed until the last minute, when the desired final size is known, to allow best quality.

If you have your icon hand-drawn in multiple sizes, use windowSetIconList. Then the best size will be used.

This function is equivalent to calling windowSetIconList with a 1-element list.

See also windowSetDefaultIconList to set the icon for all windows in your application in one go.

Sets the icon for window. Warns on failure if err is Nothing.

This function is equivalent to calling windowSetIcon with a pixbuf created by loading the image from filename.

Since: 2.2

Sets up the icon representing a Window. The icon is used when the window is minimized (also known as iconified). Some window managers or desktop environments may also place it in the window frame, or display it in other contexts. On others, the icon is not used at all, so your mileage may vary.

windowSetIconList allows you to pass in the same icon in several hand-drawn sizes. The list should contain the natural sizes your icon is available in; that is, don’t scale the image before passing it to GTK+. Scaling is postponed until the last minute, when the desired final size is known, to allow best quality.

By passing several sizes, you may improve the final image quality of the icon, by reducing or eliminating automatic image scaling.

Recommended sizes to provide: 16x16, 32x32, 48x48 at minimum, and larger images (64x64, 128x128) if you have them.

See also windowSetDefaultIconList to set the icon for all windows in your application in one go.

Note that transient windows (those who have been set transient for another window using windowSetTransientFor) will inherit their icon from their transient parent. So there’s no need to explicitly set the icon on transient windows.

Sets the icon for the window from a named themed icon. See the docs for IconTheme for more details. On some platforms, the window icon is not used at all.

Note that this has nothing to do with the WM_ICON_NAME property which is mentioned in the ICCCM.

Since: 2.6

Opens or closes the [interactive debugger][interactive-debugging], which offers access to the widget hierarchy of the application and to useful debugging tools.

Since: 3.14

Asks to keep window above, so that it stays on top. Note that you shouldn’t assume the window is definitely above afterward, because other entities (e.g. the user or [window manager][gtk-X11-arch]) could not keep it above, and not all window managers support keeping windows above. But normally the window will end kept above. Just don’t write code that crashes if not.

It’s permitted to call this function before showing a window, in which case the window will be kept above when it appears onscreen initially.

You can track the above state via the “window-state-event” signal on Widget.

Note that, according to the Extended Window Manager Hints Specification, the above state is mainly meant for user preferences and should not be used by applications e.g. for drawing attention to their dialogs.

Since: 2.4

Asks to keep window below, so that it stays in bottom. Note that you shouldn’t assume the window is definitely below afterward, because other entities (e.g. the user or [window manager][gtk-X11-arch]) could not keep it below, and not all window managers support putting windows below. But normally the window will be kept below. Just don’t write code that crashes if not.

It’s permitted to call this function before showing a window, in which case the window will be kept below when it appears onscreen initially.

You can track the below state via the “window-state-event” signal on Widget.

Note that, according to the Extended Window Manager Hints Specification, the above state is mainly meant for user preferences and should not be used by applications e.g. for drawing attention to their dialogs.

Since: 2.4

Sets the mnemonic modifier for this window.

Sets the Window:mnemonics-visible property.

Since: 2.20

Sets a window modal or non-modal. Modal windows prevent interaction with other windows in the same application. To keep modal dialogs on top of main application windows, use windowSetTransientFor to make the dialog transient for the parent; most [window managers][gtk-X11-arch] will then disallow lowering the dialog below the parent.

Request the windowing system to make window partially transparent, with opacity 0 being fully transparent and 1 fully opaque. (Values of the opacity parameter are clamped to the [0,1] range.) On X11 this has any effect only on X screens with a compositing manager running. See widgetIsComposited. On Windows it should work always.

Note that setting a window’s opacity after the window has been shown causes it to flicker once on Windows.

Since: 2.12

Sets a position constraint for this window. If the old or new constraint is WindowPositionCenterAlways, this will also cause the window to be repositioned to satisfy the new constraint.

Sets whether the user can resize a window. Windows are user resizable by default.

This function is only useful on X11, not with other GTK+ targets.

In combination with the window title, the window role allows a [window manager][gtk-X11-arch] to identify "the same" window when an application is restarted. So for example you might set the “toolbox” role on your app’s toolbox window, so that when the user restarts their session, the window manager can put the toolbox back in the same place.

If a window already has a unique title, you don’t need to set the role, since the WM can use the title to identify the window when restoring the session.

Sets the Screen where the window is displayed; if the window is already mapped, it will be unmapped, and then remapped on the new screen.

Since: 2.2

Windows may set a hint asking the desktop environment not to display the window in the pager. This function sets this hint. (A "pager" is any desktop navigation tool such as a workspace switcher that displays a thumbnail representation of the windows on the screen.)

Since: 2.2

Windows may set a hint asking the desktop environment not to display the window in the task bar. This function sets this hint.

Since: 2.2

Startup notification identifiers are used by desktop environment to track application startup, to provide user feedback and other features. This function changes the corresponding property on the underlying GdkWindow. Normally, startup identifier is managed automatically and you should only use this function in special cases like transferring focus from other processes. You should use this function before calling windowPresent or any equivalent function generating a window map event.

This function is only useful on X11, not with other GTK+ targets.

Since: 2.12

Sets the title of the Window. The title of a window will be displayed in its title bar; on the X Window System, the title bar is rendered by the [window manager][gtk-X11-arch], so exactly how the title appears to users may vary according to a user’s exact configuration. The title should help a user distinguish this window from other windows they may have open. A good title might include the application name and current document filename, for example.

Sets a custom titlebar for window.

A typical widget used here is HeaderBar, as it provides various features expected of a titlebar while allowing the addition of child widgets to it.

If you set a custom titlebar, GTK+ will do its best to convince the window manager not to put its own titlebar on the window. Depending on the system, this function may not work for a window that is already visible, so you set the titlebar before calling widgetShow.

Since: 3.10

Dialog windows should be set transient for the main application window they were spawned from. This allows [window managers][gtk-X11-arch] to e.g. keep the dialog on top of the main window, or center the dialog over the main window. gtk_dialog_new_with_buttons() and other convenience functions in GTK+ will sometimes call windowSetTransientFor on your behalf.

Passing Nothing for parent unsets the current transient window.

On Wayland, this function can also be used to attach a new GTK_WINDOW_POPUP to a GTK_WINDOW_TOPLEVEL parent already mapped on screen so that the GTK_WINDOW_POPUP will be created as a subsurface-based window GDK_WINDOW_SUBSURFACE which can be positioned at will relatively to the GTK_WINDOW_TOPLEVEL surface.

On Windows, this function puts the child window on top of the parent, much as the window manager would have done on X.

By setting the type hint for the window, you allow the window manager to decorate and handle the window in a way which is suitable to the function of the window in your application.

This function should be called before the window becomes visible.

gtk_dialog_new_with_buttons() and other convenience functions in GTK+ will sometimes call windowSetTypeHint on your behalf.

Windows may set a hint asking the desktop environment to draw the users attention to the window. This function sets this hint.

Since: 2.8

Don’t use this function. It sets the X Window System “class” and “name” hints for a window. According to the ICCCM, you should always set these to the same value for all windows in an application, and GTK+ sets them to that value by default, so calling this function is sort of pointless. However, you may want to call windowSetRole on each window in your application, for the benefit of the session manager. Setting the role allows the window manager to restore window positions when loading a saved session.

Asks to stick window, which means that it will appear on all user desktops. Note that you shouldn’t assume the window is definitely stuck afterward, because other entities (e.g. the user or [window manager][gtk-X11-arch] could unstick it again, and some window managers do not support sticking windows. But normally the window will end up stuck. Just don't write code that crashes if not.

It’s permitted to call this function before showing a window.

You can track stickiness via the “window-state-event” signal on Widget.

Asks to toggle off the fullscreen state for window. Note that you shouldn’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’t write code that crashes if not.

You can track the fullscreen state via the “window-state-event” signal on Widget.

Since: 2.2

Asks to unmaximize window. Note that you shouldn’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’t write code that crashes if not.

You can track maximization via the “window-state-event” signal on Widget.

Asks to unstick window, which means that it will appear on only one of the user’s desktops. Note that you shouldn’t assume the window is definitely unstuck afterward, because other entities (e.g. the user or [window manager][gtk-X11-arch]) could stick it again. But normally the window will end up stuck. Just don’t write code that crashes if not.

You can track stickiness via the “window-state-event” signal on Widget.

Construct a GValueConstruct with valid value for the “accept-focus” property. This is rarely needed directly, but it is used by new.

Get the value of the “accept-focus” property. When overloading is enabled, this is equivalent to

get window #acceptFocus

Set the value of the “accept-focus” property. When overloading is enabled, this is equivalent to

set window [ #acceptFocus := value ]

Set the value of the “application” property to Nothing. When overloading is enabled, this is equivalent to

clear #application

Construct a GValueConstruct with valid value for the “application” property. This is rarely needed directly, but it is used by new.

Get the value of the “application” property. When overloading is enabled, this is equivalent to

get window #application

Set the value of the “application” property. When overloading is enabled, this is equivalent to

set window [ #application := value ]

Set the value of the “attached-to” property to Nothing. When overloading is enabled, this is equivalent to

clear #attachedTo

Construct a GValueConstruct with valid value for the “attached-to” property. This is rarely needed directly, but it is used by new.

Get the value of the “attached-to” property. When overloading is enabled, this is equivalent to

get window #attachedTo

Set the value of the “attached-to” property. When overloading is enabled, this is equivalent to

set window [ #attachedTo := value ]

Construct a GValueConstruct with valid value for the “decorated” property. This is rarely needed directly, but it is used by new.