Feature Visibility - Inherited

[Paolo F Cantoni]

It would be very useful to have a separate Visibility list for inherited features.

Thus one could show all local features but a smaller subset of inherited features.

Paolo

[Paolo F Cantoni]

Related to this is the conversion of the All button to a radio button and the addition of a None radio button.

(In my standard interface, there are three radio buttons:
All, Some, None.  
When all the checkboxes are true, then All is true.  If no checkboxes are true, then None is true.  If some, but not all, checkboxes are true, then Some is true.  
Only the All and None radio buttons are enabled.  Pressing them changes the checkboxes appropriately.

In my extended interface, I also allow more radio buttons - corresponding to predefined patterns - that will set the checkboxes appropriately)

This has proved very popular with users.

HTH,
Paolo

[Jap]

I have a different yet related feature request. Namely, I would like to be able to arbitrarily select individual features (attributes, operations) of a class should appear on a class diagram. Selecting only This basic functionality that is supported in any serious UML modeling tool, e.g.IBM Rational Rose or IBM Rational Software Architect.

[Paolo F Cantoni]

I have a different yet related feature request. Namely, I would like to be able to arbitrarily select individual features (attributes, operations) of a class should appear on a class diagram. Selecting only This basic functionality that is supported in any serious UML modeling tool, e.g.IBM Rational Rose or IBM Rational Software Architect.

There is some limited support for this on a per stereotype basis - see Set Feature Visibility.  Nearly a year ago, I suggested adding the ability to hide features by tagged value.

Paolo

[Jap]

Paolo,

Thank you for information but functionality is not very convenient. Adding the feature of explicit selection of the features of a classifier to be showned on a diagram is a must. If you can influence Sparx in any way on this I would be very grateful. Generally, I appreciate EA very much but it definitely must be expanded.

<jap/>

[«Midnight»]

It might also be useful if we could limit the 'depth' (in a sort of revere sense, since we're climbing up the hierarchy) of inherited feature visibility. This could make things more tenable in deeper inheritance trees, particularly where the top few levels are part of an underlying framework - it could be used to focus on what's been added for this application, domain, etc. without displaying all the 'plumbing.'

[Paolo F Cantoni]

Paolo,

Thank you for information but functionality is not very convenient. Adding the feature of explicit selection of the features of a classifier to be showned on a diagram is a must. If you can influence Sparx in any way on this I would be very grateful. Generally, I appreciate EA very much but it definitely must be expanded.

<jap/>

Contact them directly.  I don't hold any more sway over Sparx than you do.

Paolo

[SF_lt]

half year ago I submitted request for the enhanced feature visibility, where there would be ability to select particular visible features from the list of checkboxes. Not yet implemented

Inherited feature list could be coloured differently in visilibity list.

There is some limited support for this on a per stereotype basis - see Set Feature Visibility.  Nearly a year ago, I suggested adding the ability to hide features by tagged value.

[thomaskilian]

half year ago I submitted request for the enhanced feature visibility, where there would be ability to select particular visible features from the list of checkboxes. Not yet implemented

Inherited feature list could be coloured differently in visilibity list.

Just yesterday I would have needed that