Visibility at the element level

[sargasso]

I dont know if this has been suggested before but...

I sure would like to see the ability to show or hide the contents of any container element - particluarly packages - rather than to turn it on or off for the entire diagram.

Or at least have some sort of override on an element to force the contents visible.

In many diagrams the focus is on one (or a few) elements while the remiander are included for reference at the container level only.  For example, consider a component diagram detailing the structure of a specific component - the dependencies on other components needs to be shown but only at the top level - the contents of, say, a major system dll are irrelevant, we only need to see the dependency on the component (or a particular interface thereto).

Any supporters? ...

Bruce

[Bruno.Cossi]

I second that!

Bruno

[pcleary]

Not sure if this is relevant or not, but I "third" this.  I dragged the .NET Framework System.Xml.XmlDocument class in, and it was HUGE.  I really don't need to see all those attributes and properties, but I do need them on my classes I am working on.  Visibility at an element (class, package, object, etc.) would be REALLY sweet.

[Axel]

Hello,

might this be helpful for you?

In case you have a class diagram with a number of classes, where some of them you want to show member details and some of them you want to hide them, you can do the following:
declare a default level of appearance with "visible class members" in "diagram properties" (either right mouse click on the class diagram background or in menue :diagram - properties)
Then click on the classes, where you want to have a non default appearance - and go to menue : element - set feature visibility. There you can change visibility options only for the selected class. This is not possible via right mouse context menue.

Regards

Axel.

[fluxtah]

I can agree to that, however as axel says it is possible to hide class members, which will solve that huge XmlDocument problem.

- Fluxtah

[Oscar]

As it matches my way of working, I'll support Bruce's request.

Axel's solution looks (to me) more like a workaround.

Oscar