Bug 5624 - Toggling public/private in assembly browser doesn't take effect immediately
Summary: Toggling public/private in assembly browser doesn't take effect immediately
Status: RESOLVED FIXED
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Assembly browser ()
Version: Trunk
Hardware: PC Mac OS
: Normal normal
Target Milestone: ---
Assignee: Mike Krüger
URL:
Depends on:
Blocks:
 
Reported: 2012-06-12 17:25 UTC by Mikayla Hutchinson [MSFT]
Modified: 2012-10-10 02:39 UTC (History)
2 users (show)

Tags:
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:
Status:
RESOLVED FIXED

Description Mikayla Hutchinson [MSFT] 2012-06-12 17:25:55 UTC
Toggling the public/private setting in the assembly browser doesn't take effect immediately, only after closing and reopening it.

The assembler browser should use options (they're now global, not per-node) instead of implementing its own.
Comment 1 Mike Krüger 2012-06-13 03:52:56 UTC
Works for me:

http://screencast.com/t/iUGFyBv2vV


Why should it use these options ? Where is the benefit ?
Comment 2 Mikayla Hutchinson [MSFT] 2012-06-13 13:40:58 UTC
Hm, now I can't reproduce, same build. But it definitely happened multiple times, so I've leaving it open.

The reason I suggested using the options is that there's less code and a single implementation to debug.
Comment 3 Mike Krüger 2012-06-14 01:37:23 UTC
I'm not really happy with the speed of the tree - therefore I don't want to dig deeper into the extensible tree view code again.

When I'm in the mood & have some time I want to make an own control for showing the tree. 

If the 'Refresh' method from the treeview works - the update works.
Comment 4 Mike Krüger 2012-06-14 01:37:40 UTC
Reopen if you have a way to reproduce that.
Comment 5 Miguel de Icaza [MSFT] 2012-07-27 08:44:44 UTC
With MonoDevelop 3.0.4.1, using the assembly browser to browse List<T>, or any of the MonoTouch types.

Notice how private members are being rendered, despite the setting:

http://tirania.org/s/e3616f97.png

It seems like the combobox merely affects whether types are shown or not, it does not affect the rendering of the decompiled text, which always shows the private members.
Comment 6 Mike Krüger 2012-10-10 02:39:53 UTC
already fixed