Commit 074f391f authored by Matthias Clasen's avatar Matthias Clasen

Make GTK_DEBUG=interactive work better

We currently have various ways to initialize GTK+, and not
all of them were supporting this way of bringing up the
inspector. Fix this.

https://bugzilla.gnome.org/show_bug.cgi?id=776807
parent ea4af401
......@@ -809,6 +809,9 @@ post_parse_hook (GOptionContext *context,
return FALSE;
}
if (gtk_get_debug_flags () & GTK_DEBUG_INTERACTIVE)
gtk_window_set_interactive_debugging (TRUE);
}
return TRUE;
......@@ -988,7 +991,15 @@ gtk_init_with_args (gint *argc,
return FALSE;
done:
return GDK_PRIVATE_CALL (gdk_display_open_default) () != NULL;
if (GDK_PRIVATE_CALL (gdk_display_open_default) () != NULL)
{
if (gtk_get_debug_flags () & GTK_DEBUG_INTERACTIVE)
gtk_window_set_interactive_debugging (TRUE);
return TRUE;
}
return FALSE;
}
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment