After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 752664 - Inspector only shows widget tree if created after startup
Inspector only shows widget tree if created after startup
Status: RESOLVED FIXED
Product: gtk+
Classification: Platform
Component: Debugging
3.16.x
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2015-07-21 12:16 UTC by Jonny Lamb
Modified: 2015-07-24 02:00 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Jonny Lamb 2015-07-21 12:16:26 UTC
Using GTK_DEBUG=interactive (or --gtk-debug=interactive) when starting an app pops up the inspector fine. However, the widget tree is in the object list.

Using the keyboard shortcut while the app is already running to show the inspector doesn't have this problem and the object list is full of the toplevel windows and the widgets inside said toplevel.

In the environment variable case, gtk_window_list_toplevels() is probably being called before any toplevels have been created, whereas using the keyboard shortcut ensures the toplevel is present before the inspector is created.
Comment 1 Matthias Clasen 2015-07-23 19:01:48 UTC
Given that the inspector is already tied into gtkwindow.c, we could just make it rescan whenever we update the toplevel list.