Description Peter Cigehn 2016-03-31 09:41:16 EDT

For users who have a need to mix UML-RT with standard UML in the same model, e.g. high level system modeling, or users creating intermixed DSMLS on top of UML-RT, it becomes a bit confusing when the filtering of the new child menu which only should be applicable on the UMLRealTime new child menu, also seem to be done on the standard new child menu.

One concrete example is the lack of possibility of creating a port for a normal class. On the UMLRealTime new child menu it is expected that is should not be possible to create a port on a normal class (since it does not make sense in the UML-RT context). But if the user uses the standard new child menu, the user probably expects the normal possibilities according to base UML.

This becomes even more confusing, when the filtering also "spills over" to other meta-classes, completely unrelated to UML-RT, e.g. component which also incorrectly gets its menu choice for creating a port filtered. Users who wants to mix UML-RT with "ordinary" component modeling, will then be prohibited from creating ports on components.

The filtering on the UMLRealTime new child menu, should preferably *only* be applicable to that new child menu, to avoid confusion. See Bug 469677 for the initial proposal of how the UMLRealTime new child menu should look like. Any filtering needed for this new child menu should only be applicable for that new child menu, and not for the standard UML new child menu.