Memory-managed wrapper type.

Type class for types which can be safely cast to Dialog, for instance with toDialog.

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

Adds an activatable widget to the action area of a Dialog, connecting a signal handler that will emit the response signal on the dialog when the widget is activated. The widget is appended to the end of the dialog’s action area. If you want to add a non-activatable widget, simply pack it into the actionArea field of the Dialog struct.

Adds a button with the given text and sets things up so that clicking the button will emit the response signal with the given responseId. The button is appended to the end of the dialog’s action area. The button widget is returned, but usually you don’t need it.

Returns the action area of dialog.

Since: 2.14

Returns the content area of dialog.

Since: 2.14

Returns the header bar of dialog. Note that the headerbar is only used by the dialog if the Dialog:use-header-bar property is True.

Since: 3.12

Gets the response id of a widget in the action area of a dialog.

Since: 2.8

Gets the widget button that uses the given response ID in the action area of a dialog.

Since: 2.20

Creates a new dialog box.

Widgets should not be packed into this Window directly, but into the vbox and actionArea, as described above.

Emits the response signal with the given response ID. Used to indicate that the user has responded to the dialog in some way; typically either you or dialogRun will be monitoring the response signal and take appropriate action.

Blocks in a recursive main loop until the dialog either emits the response signal, or is destroyed. If the dialog is destroyed during the call to dialogRun, dialogRun returns GTK_RESPONSE_NONE. Otherwise, it returns the response ID from the response signal emission.

Before entering the recursive main loop, dialogRun calls widgetShow on the dialog for you. Note that you still need to show any children of the dialog yourself.

During dialogRun, the default behavior of deleteEvent is disabled; if the dialog receives delete_event, it will not be destroyed as windows usually are, and dialogRun will return GTK_RESPONSE_DELETE_EVENT. Also, during dialogRun the dialog will be modal. You can force dialogRun to return at any time by calling dialogResponse to emit the response signal. Destroying the dialog during dialogRun is a very bad idea, because your post-run code won’t know whether the dialog was destroyed or not.

After dialogRun returns, you are responsible for hiding or destroying the dialog if you wish to do so.

Typical usage of this function might be:

C code

 GtkWidget *dialog = gtk_dialog_new ();
 // Set up dialog...

 int result = gtk_dialog_run (GTK_DIALOG (dialog));
 switch (result)
   {
     case GTK_RESPONSE_ACCEPT:
        // do_application_specific_something ();
        break;
     default:
        // do_nothing_since_dialog_was_cancelled ();
        break;
   }
 gtk_widget_destroy (dialog);

Note that even though the recursive main loop gives the effect of a modal dialog (it prevents the user from interacting with other windows in the same window group while the dialog is run), callbacks such as timeouts, IO channel watches, DND drops, etc, will be triggered during a dialogRun call.

Sets an alternative button order. If the Settings:gtk-alternative-button-order setting is set to True, the dialog buttons are reordered according to the order of the response ids in newOrder.

See gtk_dialog_set_alternative_button_order() for more information.

This function is for use by language bindings.

Since: 2.6

Sets the last widget in the dialog’s action area with the given responseId as the default widget for the dialog. Pressing “Enter” normally activates the default widget.

Calls gtk_widget_set_sensitive (widget, @setting) for each widget in the dialog’s action area with the given responseId. A convenient way to sensitize/desensitize dialog buttons.

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

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

get dialog #useHeaderBar

Type for the callback on the (unwrapped) C side.

The close signal is a [keybinding signal][GtkBindingSignal] which gets emitted when the user uses a keybinding to close the dialog.

The default binding for this signal is the Escape key.

Connect a signal handler for the close signal, to be run after the default handler. When overloading is enabled, this is equivalent to

after dialog #close callback

Wrap the callback into a GClosure.

Generate a function pointer callable from C code, from a C_DialogCloseCallback.

A convenience synonym for Nothing :: Maybe DialogCloseCallback.

Connect a signal handler for the close signal, to be run before the default handler. When overloading is enabled, this is equivalent to

on dialog #close callback

Wrap a DialogCloseCallback into a C_DialogCloseCallback.

Type for the callback on the (unwrapped) C side.

Emitted when an action widget is clicked, the dialog receives a delete event, or the application programmer calls dialogResponse. On a delete event, the response ID is GTK_RESPONSE_DELETE_EVENT. Otherwise, it depends on which action widget was clicked.

Connect a signal handler for the response signal, to be run after the default handler. When overloading is enabled, this is equivalent to

after dialog #response callback

Wrap the callback into a GClosure.

Generate a function pointer callable from C code, from a C_DialogResponseCallback.

A convenience synonym for Nothing :: Maybe DialogResponseCallback.

Connect a signal handler for the response signal, to be run before the default handler. When overloading is enabled, this is equivalent to

on dialog #response callback

Wrap a DialogResponseCallback into a C_DialogResponseCallback.