Community
Participate
Working Groups
The OCL Console exploits a selection of a 'self' object in the UML model editor to allow OCL expression evaluation on UML models. One of my users got in a mess trying to practice Stereotype constraints since there is no selectable stereotype instance. The workaround is to select the stereotyped instance and prefix the OCL evaluation with self.extension_Stereotype... The UML Model Editor would be more powerful if the stereotype instance was selectable. Selecting <<Stereotype>> is ergonomically inconsistent and probably rather hard in the Tree editor, so: I suggest that each stereotype instance has a tree-child similar to that for Ecore superclasses and types. This tree-child could then be selected to define the stereotype instance as the selection for 'self' and clearly view the stereotype properties in the Properties View.
