Closed cdamus closed 5 years ago
Thanks, @tortmayr!
I'll have to look into the argument problem. Probably all concrete ValueSpecification
metaclasses are filtered out. 😕 Good point about the destruction occurrence. Hiding the buttons for the read-only reference properties will require custom property-editor widgets; should be simple to do.
Happily, it was not necessary to create a custom property editor to suppress the edit buttons in the read-only reference properties. All that was needed was to customize the isMandatory
and getDirectCreation
queries in the model element façade.
Implement the property views for elements in the UML Light Sequence Diagram. This includes a custom
ModelElement
implementation that provides for filtering ofEClass
es that may be instantiated for creation of new elements via the green ➕ buttonThe former is applied to filtering of allowed
MessageSort
values for messages. The latter is implemented generically for all of the diagrams.Any other customization of the edit behaviour in the Properties View can be integrated in this
UMLLightModelElement
, possibly with the assistance of more custom editor widgets like the custom multiplicity editor.