You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You can see the import icon on the inheritance arrow in the left diagram. To reproduce:
Create a new 'Ecore Modeling Project'. Name it test. Accept defaults.
Create a new 'Ecore Model' in the same model directory, naming it test2.
Name the package in test2 also test2.
Add a class diagram representation also for test2.
Add a class named Class1 to test using the diagram editor.
Add a class named Class2 to test2 using the diagram editor.
Save both diagrams.
Add each class to the other diagram, using the 'Add' tool from the 'Existing Elements' part of the palette.
Add an inheritance relation from one class to another, in one of the diagrams, using the 'SuperType' tool.
Note how in one of the diagram the inheritance arrow shows with an import icon.
I get the import icon on imported classes, and find it useful. But it just looks weird an confusing on the arrow, in my opinion. Especially if you have a tree of inheritance relations, like this example from a metamodel in the Eclipse ESCET project:
The corresponding decorator is defined to match any graphical element which represents a "remote" EClassifier.
Because the inheritance edges correspond to a raw reference (and not a reified EObject), it is associated to its source EClass, so matches the condition.
I'll have to check, but I think the preconditionExpression on the decorator definition has access to enough information to exclude edges.
It looks something like this:
You can see the import icon on the inheritance arrow in the left diagram. To reproduce:
test
. Accept defaults.model
directory, naming ittest2
.test2
alsotest2
.test2
.Class1
totest
using the diagram editor.Class2
totest2
using the diagram editor.I get the import icon on imported classes, and find it useful. But it just looks weird an confusing on the arrow, in my opinion. Especially if you have a tree of inheritance relations, like this example from a metamodel in the Eclipse ESCET project:
(originally reported at: eclipse-emf/org.eclipse.emf#12)
The text was updated successfully, but these errors were encountered: