gtk:widget, gobject:initially-unowned, gtk:accessible, gtk:buildable, gtk:constraint-target, gtk:native, gtk:root, gtk:shortcut-manager, gobject:object, common-lisp:standard-object, common-lisp:t

gtk:about-dialog, gtk:application-window, gtk:assistant, gtk:dialog, gtk:shortcuts-window

The gtk:window widget is a toplevel window which can contain other widgets.

Figure: GtkWindow

Windows normally have decorations that are under the control of the windowing system and allow the user to manipulate the window, for example, to resize it, move it, or close it. The gtk:window implementation of the gtk:buildable interface supports setting a child widget as the titlebar by specifying titlebar as the type attribute of a <child> element.

window.background [.csd / .solid-csd / .ssd] [.maximized / .fullscreen / .tiled]
├── <child>
╰── <titlebar child>.titlebar [.default-decoration]    

The gtk:window implementation has a main CSS node with name window and .background style class.

Style classes that are typically used with the main CSS node are .csd, when client-side decorations are in use, .solid-csd, for client-side decorations without invisible borders, .ssd, used by mutter when rendering server-side decorations. The gtk:window implementation also represents window states with the following style classes on the main node: .tiled, .maximized, .fullscreen. Specialized types of window often add their own discriminating style classes, such as .popup or .tooltip.

Generally, some CSS properties do not make sense on the toplevel window node, such as margins or padding. When client-side decorations without invisible borders are in use, that is, the .solid-csd style class is added to the main window node, the CSS border of the toplevel window is used for resize drags. In the .csd case, the shadow area outside of the window can be used to resize it.

The gtk:window implementation adds the .titlebar and .default-decoration style classes to the widget that is added as a titlebar child. The gtk:window implementation uses the :window role of the gtk:accessible-role enumeration.

The "activate-default" signal

lambda (window)    :action      

window

The gtk:window widget which received the signal.

The signal is a keybinding signal which gets emitted when the user activates the default widget of the window.

The "activate-focus" signal

lambda (window)    :action      

window

The gtk:window widget which received the signal.

The signal is a keybinding signal which gets emitted when the user activates the currently focused widget of the window.

The "close-request" signal

lambda (window)    :run-last      

window

The gtk:window widget on which the signal is emitted.

Returns

True to stop other handlers from being invoked for the signal.

The signal is emitted when the user clicks on the close button of the window.

The "enable-debugging" signal

lambda (window toggle)    :action      

window

The gtk:window widget on which the signal is emitted.

toggle

The boolean which toggles the debugger.

Returns

The boolean which is true if the key binding was handled.

The signal is a keybinding signal which gets emitted when the user enables or disables interactive debugging. When the toggle argument is true, interactive debugging is toggled on or off, when it is false, the debugger will be pointed at the widget under the pointer. The default bindings for this signal are the Ctrl-Shift-I and Ctrl-Shift-D keys.

The "keys-changed" signal

lambda (window)    :run-first      

window

The gtk:window widget which received the signal.

The signal gets emitted when the set of accelerators or mnemonics that are associated with the window changes.
Warning: Deprecated since 4.10. Use gtk:shortcut and gtk:event-controller objects to implement keyboard shortcuts.