Bug 449 - object inspector is not reliable
Summary: object inspector is not reliable
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Debugger ()
Version: unspecified
Hardware: PC Mac OS
: --- normal
Target Milestone: 2.8.1
Assignee: Bugzilla
Depends on:
Reported: 2011-08-25 16:31 UTC by Rodrigo Kumpera
Modified: 2011-12-14 18:31 UTC (History)
4 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description Rodrigo Kumpera 2011-08-25 16:31:06 UTC
I found two issues with the object inspector.

First, the timeout to fade it way is too small, sometime I can't get to click somewhere to expand before it goes away.

Clicking to expand any information is not reliable and most of the times it closes the inspector. To reproduce this, start with the app from http://docs.xamarin.com/ios/getting_started/Hello_iPhone

Set a breakpoint on the first line of the both of actnButtonClick.

Debug the and click on any of the button on the second line. This will cause the breakpoint to be hit.

Inspect lblOutput from the statement just hit.

Click to expand it.

Clicking to expand anything else will cause the inspection to close for no reason.
Comment 1 Rodrigo Kumpera 2011-08-25 16:32:00 UTC
Oh, there's another issue.

If I inspect lblOutput, click to pin it and ask it to expand, it will show behind the watch panel instead on top.
Comment 2 Rodrigo Kumpera 2011-08-30 11:37:44 UTC
Another point here.

When expanding fails for no apparent reason, it would be nice to somehow know what went wrong, even if it's only to help others of us fix the underlying issue.
Comment 3 Jeffrey Stedfast 2011-12-14 12:04:28 UTC
Wow... this seems like a gtk bug to me.

Anyways, it's not quite so simple to reproduce. When I first did this, the expanded tree window was on top of the Watch window, but if I switched to another tab (like Threads), then the tree window would be drawn behind that pad. Switching back to the Watch tab doesn't fix it, either. Nor does collapsing and then re-expanding the tree window.
Comment 4 Jeffrey Stedfast 2011-12-14 12:06:13 UTC
Interestingly, if I right-click inside of the tree window, it pops to the top again.
Comment 5 Jeffrey Stedfast 2011-12-14 12:06:53 UTC
actually, left-clicking on the tree-window works too. So it's simply the act of focusing it that brings it to the top.
Comment 6 Jeffrey Stedfast 2011-12-14 18:31:41 UTC
So the wacky rendering issues I was seeing were do to a change to workaround a bug in Gdk/Gtk on Win32 due to children not getting unmapped/mapped.

So... back to the original bug.

The fact that the pinned treeview appears behind the watch pad is not actually a bug. HOWEVER!! This does expose the following bug: bug #2506 (pinned watches are not scrollable)