[gtk/ebassi/run-dialog-run: 12/22] Remove gtk_dialog_run() from GtkMountOperation
- From: Emmanuele Bassi <ebassi src gnome org>
- To: commits-list gnome org
- Cc:
- Subject: [gtk/ebassi/run-dialog-run: 12/22] Remove gtk_dialog_run() from GtkMountOperation
- Date: Thu, 30 Apr 2020 17:56:17 +0000 (UTC)
commit 2b64ec1b12ad1123aef5495baef7013a92891557
Author: Emmanuele Bassi <ebassi gnome org>
Date: Thu Apr 30 13:43:17 2020 +0100
Remove gtk_dialog_run() from GtkMountOperation
gtk/gtkmountoperation.c | 9 +--------
1 file changed, 1 insertion(+), 8 deletions(-)
---
diff --git a/gtk/gtkmountoperation.c b/gtk/gtkmountoperation.c
index d1eb782079..6f51e7ea2e 100644
--- a/gtk/gtkmountoperation.c
+++ b/gtk/gtkmountoperation.c
@@ -1372,7 +1372,6 @@ on_end_process_activated (GtkModelButton *button,
if (!_gtk_mount_operation_kill_process (pid_to_kill, &error))
{
GtkWidget *dialog;
- gint response;
/* Use GTK_DIALOG_DESTROY_WITH_PARENT here since the parent dialog can be
* indeed be destroyed via the GMountOperation::abort signal... for example,
@@ -1389,14 +1388,8 @@ on_end_process_activated (GtkModelButton *button,
error->message);
gtk_widget_show (dialog);
- response = gtk_dialog_run (GTK_DIALOG (dialog));
- /* GTK_RESPONSE_NONE means the dialog were programmatically destroy, e.g. that
- * GTK_DIALOG_DESTROY_WITH_PARENT kicked in - so it would trigger a warning to
- * destroy the dialog in that case
- */
- if (response != GTK_RESPONSE_NONE)
- gtk_widget_destroy (dialog);
+ g_signal_connect (dialog, "response", G_CALLBACK (gtk_widget_destroy), NULL);
g_error_free (error);
}
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]