[nautilus-actions] Add a comment about the new dialogs behavior



commit e1d5af0c839f24840430fb6cfcf31102dc59e376
Author: Pierre Wieser <pwieser trychlos org>
Date:   Thu Jul 9 17:21:39 2015 +0200

    Add a comment about the new dialogs behavior

 src/nact/base-window.c |   14 ++++++++++++++
 1 files changed, 14 insertions(+), 0 deletions(-)
---
diff --git a/src/nact/base-window.c b/src/nact/base-window.c
index 2f5e7e3..49b3bda 100644
--- a/src/nact/base-window.c
+++ b/src/nact/base-window.c
@@ -843,6 +843,20 @@ do_initialize_base_window( BaseWindow *window )
 
                g_debug( "%s: window=%p (%s)", thisfn, ( void * ) window, G_OBJECT_TYPE_NAME( window ));
 
+               /* pwi 2015- 6-25
+                * Making the child window transient regarding its parent make
+                * these two windows attached, and the user is no more able to
+                * move the child without also moving the parent :(
+                * THIS IS A BAD GTK+ CHOICE.
+                * More, modifying this settings requires the TweakSettings tool
+                * which is not even part of the core distribution.
+                * See: Windows - Attached modal dialogs.
+                *
+                * When transient is not set, the user will now get a message:
+                *   Gtk-Message: GtkDialog mapped without a transient parent.
+                *   This is discouraged.
+                * THIS IS A BAD GTK+ CHOICE.
+                */
                if( priv->main_window ){
                        g_return_if_fail( GTK_IS_APPLICATION_WINDOW( priv->main_window ));
                        gtk_window_set_transient_for( priv->gtk_toplevel, GTK_WINDOW( priv->main_window ));


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]