Hide private members should be a setting, not a tool

[GeertvanHorrik]

I think that if VisibilitySettings.HidePrivateMembers is a setting (and thus can be determined dynamically), it works much better than using it as a tool (where clicking the button does the calculation of a moment in time).

What do you think?

[GeertvanHorrik]

I see it's also stored as a property. Not sure why the need for explicitly writing the identifiers out is needed.

[geaz]

In fact HidePrivateMembers is a property which gets checked during the parse step. They are included in the ExcludedIdentifiers property for the correct visualization in the UI at the moment. It is an old mechanism and could be replaced in the future.