+@var{event}: a @ref{event-key}
+
+@RMethod window-present
+@lisp
+(window-present window)
+@end lisp
+
+Presents a @var{window} (a @ref{gtk-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 @ref{widget-show} 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 @ref{window-present} 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 @ref{window-present-with-time}.
+
+@RMethod window-present-with-time
+@lisp
+(window-present-with-time window timestamp)
+@end lisp
+
+Presents a @var{window} (a @ref{gtk-window}) to the user in response to a user interaction. If you need to present a window without a timestamp, use @ref{window-present}. See @ref{window-present} for details.
+
+@var{timestamp}: the timestamp of the user interaction (typically a button or key press event) which triggered this call
+
+@RMethod window-iconify
+@lisp
+(window-iconify window)
+@end lisp
+
+Asks to iconify (i.e. minimize) the specified @var{window} (a @ref{gtk-window}). Note that you shouldn't assume the window is definitely iconified afterward, because other entities (e.g. the user or window manager) 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 @SignalRef{widget,window-state-event} signal on GtkWidget.
+
+@RMethod window-deiconify
+@lisp
+(window-deiconify window)
+@end lisp
+
+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) could iconify it again before your code which assumes deiconification gets to run.
+
+You can track iconification via the @SignalRef{widget,window-state-event}.
+
+@RMethod window-stick
+@lisp
+(window-stick window)
+@end lisp
+Asks to stick @var{window} (a @ref{gtk-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) 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 @SignalRef{widget,window-state-event} signal.
+
+@RMethod window-unstick
+@lisp
+(window-unstick window)
+@end lisp
+Asks to unstick @var{window} (a @ref{gtk-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) 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 @SignalRef{widget,window-state-event} signal.
+
+@RMethod window-maximize
+@lisp
+(window-maximize window)
+@end lisp
+
+Asks to maximize @var{window} (a @ref{gtk-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) 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 @SignalRef{widget,window-state-event} signal.
+
+@RMethod window-unmaximize
+@lisp
+(window-unmaximize window)
+@end lisp
+
+Asks to unmaximize @var{window} (a @ref{gtk-window}). Note that you shouldn't assume the window is definitely unmaximized afterward, because other entities (e.g. the user or window manager) 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 @SignalRef{widget,window-state-event} signal on GtkWidget.
+
+@RMethod window-fullscreen
+@lisp
+(window-fullscreen window)
+@end lisp
+
+Asks to place @var{window} (a @ref{gtk-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) 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 @SignalRef{widget,window-state-event} signal.
+
+@RMethod window-unfullscreen
+@lisp
+(window-unfullscreen window)
+@end lisp
+
+Asks to toggle off the fullscreen state for @var{window} (a @ref{gtk-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) 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 @SignalRef{widget,window-state-event} signal.
+
+@RMethod window-set-keep-above
+@lisp
+(window-set-keep-above window setting)
+@end lisp
+
+Asks to keep @var{window} (a @ref{gtk-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) 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 @SignalRef{widget,window-state-event} signal.
+
+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.
+
+@var{setting}: a boolean; whether to keep @var{window} above other windows
+
+@RMethod window-set-keep-below
+@lisp
+(window-set-keep-below window setting)
+@end lisp
+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) 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 GtkWidget.
+
+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.
+
+@var{setting}: a boolean; whether to keep window below other windows
+
+@RMethod window-begin-resize-drag
+@lisp
+(window-begin-resize-drag window edge button root-x root-y timestamp)
+@end lisp
+
+Starts resizing a @var{window} (a @ref{gtk-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 or windowing system. Otherwise, GDK will try to emulate window resizing, potentially not all that well, depending on the windowing system.
+
+@var{edge}: a @ref{window-edge}; position of the resize control
+
+@var{button}: an integer; mouse button that initiated the drag
+
+@var{root-x}: an integer; X position where the user clicked to initiate the drag, in root window coordinates
+
+@var{root-y}: an integer; Y position where the user clicked to initiate the drag
+
+@var{timestamp}: timestamp from the click event that initiated the drag
+
+@RMethod window-begin-move-drag
+@lisp
+(window-begin-move-drag window button root-x root-y timestamp)
+@end lisp
+
+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 or windowing system. Otherwise, GDK will try to emulate window movement, potentially not all that well, depending on the windowing system.
+
+@var{edge}: a @ref{window-edge}; position of the resize control
+
+@var{button}: an integer; mouse button that initiated the drag
+
+@var{root-x}: an integer; X position where the user clicked to initiate the drag, in root window coordinates
+
+@var{root-y}: an integer; Y position where the user clicked to initiate the drag
+
+@var{timestamp}: timestamp from the click event that initiated the drag
+
+@RMethod window-set-frame-dimensions
+@lisp
+(window-set-frame-dimensions window left top right bottom)
+@end lisp
+
+(Note: this is a special-purpose function intended for the framebuffer port; see @ref{window-set-has-frame}. It will have no effect on the window border drawn by the window manager, which is the normal case when using the X Window system.)
+
+For windows with frames this function can be used to change the size of the frame border.
+
+@var{window}: a @ref{gtk-window}
+
+@var{left}, @var{top}, @var{right}, @var{bottom} - integers; sizes of left, top, right, bottom borders
+
+@RMethod window-set-has-frame
+@lisp
+(window-set-has-frame window setting)
+@end lisp
+
+(Note: this is a special-purpose function for the framebuffer port, that causes GTK+ to draw its own window border. For most applications, you want @SlotRef{gtk-window,decorated} instead, which tells the window manager whether to draw the window border.)
+
+If this function is called on a @var{window} (a @ref{gtk-window}) with setting of True, before it is realized or showed, it will have a "frame" window around window->window, accessible in window->frame. Using the signal @SignalRef{gtk-window,frame-event} you can receive all events targeted at the frame.
+
+This function is used by the linux-fb port to implement managed windows, but it could conceivably be used by X-programs that want to do their own window decorations.
+
+@var{setting}: a boolean
+
+@RMethod window-set-mnemonic-modifier
+@lisp
+(window-set-mnemonic-modifier window modifier)
+@end lisp
+
+Sets the mnemonic @var{modifier} (a @ref{modifier-type}) for this @var{window} (a @ref{gtk-window}).
+
+@Function window-default-icon-list
+@lisp
+(setf (window-default-icon-list) icons)
+@end lisp
+
+Sets an icon list to be used as fallback for windows that haven't had @code{gtk_window_set_icon_list} set 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.
+
+@var{icons}: a list of @ref{pixbuf}s.
+
+@Function window-default-icon
+@lisp
+(setf (window-default-icon) icon)
+@end lisp
+
+Sets an @var{icon} (a @ref{pixbuf}) to be used as fallback for windows that haven't had @SlotRef{gtk-window,icon} set on them from a pixbuf.
+
+@Function window-default-icon-name
+@lisp
+(setf (window-default-icon-name) name)
+@end lisp
+
+Sets an icon (a @code{string} - the name of the themed icon) to be used as fallback for windows.
+
+@RMethod window-move
+@lisp
+(window-move window x y)
+@end lisp
+
+Asks the window manager to move @var{window} (a @ref{gtk-window}) to the given position (defined by integers @var{x}, @var{y}). 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 @EnumVRef{gravity,north-west}, so the reference point is simply the x, y supplied. 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 @EnumVRef{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 @EnumVRef{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 at http://www.freedesktop.org/Standards/wm-spec has a nice table of gravities in the "implementation notes" section.
+
+@RMethod window-resize
+@lisp
+(window-resize window width height)
+@end lisp
+
+Resizes the @var{window} (a @ref{gtk-window}) to @var{width} pixels by @var{height} pixels 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 (see @SlotRef{widget,width-request}, @SlotRef{widget,height-request}).
+
+If @ref{window-resize} is called before showing a window for the first time, it overrides any default size set with @SlotRef{gtk-window,default-width}, @SlotRef{gtk-window,default-height}.
+
+Windows may not be resized smaller than 1 by 1 pixels.