gtk.Dialog.add_action_widget

    def add_action_widget(child, response_id)

The add_action_widget() method adds an activatable widget to the action area of a gtk.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 action_area.

gtk.Dialog.add_button

    def add_button(button_text, response_id)

The add_button() method adds a button with the text specified by button_text (or a stock button, if button_text is a stock ID) and sets things up so that clicking the button will emit the "response" signal with the specified response_id. 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.

gtk.Dialog.add_buttons

    def add_buttons(...)

The add_buttons() method adds several buttons to the gtk.Dialog using the button data passed as arguments to the method. This method is the same as calling the gtk.Dialog.add_button() repeatedly. The button data pairs - button text (or stock ID) and a response ID integer are passed individually. For example:

  dialog.add_buttons(gtk.STOCK_OPEN, 42, "Close", gtk.RESPONSE_CLOSE)

will add "Open" and "Close" buttons to dialog.

gtk.Dialog.set_response_sensitive

    def set_response_sensitive(response_id, setting)

The set_response_sensitive() method calls the gtk.Window.set_sensitive() method with the specified response_id for each widget in the dialog's action area. This method is a convenience function to sensitize/desensitize all dialog buttons at once.

gtk.Dialog.set_default_response

    def set_default_response(response_id)

The set_default_response() method sets the last widget in the dialog's action area with the specified response_id as the default widget for the dialog. Pressing Enter normally activates the default widget.

gtk.Dialog.set_has_separator

    def set_has_separator(setting)

The set_has_separator() method sets the "has-separator" property to the value of setting. If setting is TRUE (the default value) the dialog has a separator above the buttons.

gtk.Dialog.get_has_separator

    def get_has_separator()

The get_has_separator() method returns the value of the "has-separator" property.

gtk.Dialog.response

    def response(response_id)

The response() method emits the "response" signal with the value specified in response_id. This method is used to indicate that the user has responded to the dialog in some way; typically either you or gtk.Dialog.run() will be monitoring the "response" signal and take appropriate action.

gtk.Dialog.run

    def run()

The run() method blocks in a recursive main loop until the dialog either emits the "response" signal, or is destroyed. If the dialog is destroyed, the run() method returns gtk.RESPONSE_NONE; otherwise, it returns the response ID from the "response" signal emission. Before entering the recursive main loop, the run() method calls the gtk.Widget.show() on the dialog for you. Note that you still need to show any children of the dialog yourself.

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

After the run() method returns, you are responsible for hiding or destroying the dialog as needed.

gtk.Dialog.set_alternative_button_order

    def set_alternative_button_order(new_order)

The set_alternative_button_order() method sets an alternative button order for the dialog based on the sequence of response ids specified by new_order. If the "gtk-alternative-button-order" property of the gtk.Settings object is set to TRUE, the dialog buttons are reordered according to the order of the response ids passed to this method.

By default, GTK+ dialogs use the button order advocated by the Gnome Human Interface Guidelines with the affirmative button at the far right, and the cancel button left of it. But the builtin GTK+ dialogs and gtk.MessageDialogs do provide an alternative button order, which is more suitable on some platforms, e.g. Windows.

Use this method after adding all the buttons to your dialog, as the following example shows:

  settings = gtk.settings_get_default()
  settings.set_property('gtk-alternative-button-order', True)

  dialog = gtk.Dialog()
  cancel_button = dialog.add_button(gtk.STOCK_CANCEL, gtk.RESPONSE_CANCEL)
  ok_button = dialog.add_button(gtk.STOCK_OK, gtk.RESPONSE_OK)
  ok_button.grab_default()
  help_button = dialog.add_button(gtk.STOCK_HELP, gtk.RESPONSE_HELP)

  dialog.set_alternative_button_order([gtk.RESPONSE_OK, gtk.RESPONSE_CANCEL,
                                       gtk.RESPONSE_HELP])

gtk.Dialog.get_response_for_widget

    def get_response_for_widget(widget)

The get_response_for_widget() method returns the response id of the widget specified by widget in the action area of the dialog.

gtk.alternative_dialog_button_order

    def gtk.alternative_dialog_button_order(screen=None)

The gtk.alternative_dialog_button_order() returns TRUE if the alternative button order should be used for the gtk.gdk.Screen specified by screen. If screen is None the default gtk.gdk.Screen is used.

The "close" gtk.Dialog Signal

    def callback(dialog, user_param1, ...)

The "close" signal is emitted when the dialog is closed.

The "response" gtk.Dialog Signal

    def callback(dialog, response_id, user_param1, ...)

The "response" signal is emitted when an action_area widget is activated (button "clicked"), the dialog receives a delete_event or the application calls the response() method. When a delete_event triggers the "response" signal the response_id will be gtk.RESPONSE_NONE.