| Workaround for Execution of Creation Tools on different Container [message #1749089] |
Thu, 01 December 2016 17:47  |
 Matt Se
Messages: 29
Registered: February 2016 |
Junior Member |
|
|
The graphical representation hierachy of my diagram differs from the actual meta-model containment architecture.
For example, my diagram displays a parent EObject "A" and its containing EObjects "B" in the same sirius graphical container diagram element "C".
So B.eContainer() == A, but both are represented in the same sirius container diagram element C.
Now I can't execute a palette creation Tool for B on the graphical A element (which is B's EObject container), but only on C (which is B's diagram elements container).
I implemented a workaround by implementing a dummy Node Diagram inside A and then the Node Creation tool simply creates a B instance.
This seems ok though, but the problem appears to be that there is no new LayoutData set inside the C diagram element, so that the newly created B diagram element bounces around in the diagram...
I could intercept the location where the Node Creation is executed and add a corresponding new LayoutData for C container, but that's messy...
Is there a solution for this problem? Is it possible to enable a Creation Tool to be executed on an arbitrary diagram container?
Thanks in advance!
[Updated on: Thu, 01 December 2016 17:48] Report message to a moderator |
|
|
|
Powered by
FUDForum. Page generated in 0.03219 seconds
] 
Search
Help
Register
Login
Home
