Eclipse Community Forums: GMF (Graphical Modeling Framework) » Containers of Contains Behaving Weird

Home » Modeling » GMF (Graphical Modeling Framework) » Containers of Contains Behaving Weird(GMF Containers)

Containers of Contains Behaving Weird [message #663350]

Mon, 04 April 2011 13:53

Eclipse User

I have created a simple GMF library based off the Library EMF Model. I've modified it such that a library can contain a Library and I created another root object Bookstore that also contains Books.

For one when I create a Diagram based off this model I get lots of duplicate Edit Parts. For example:
LibraryEditPart
Library2EditPart

Secondly, I get strange behavior whenever I drag a sub library out into the root context. I get two libraries to show up in the root context.

I can update load the sample projects somewhere to anyone if if think it would help.

Re: Containers of Contains Behaving Weird [message #663369 is a reply to message #663350]

Mon, 04 April 2011 15:31

Eclipse User

Hi,

Erik Englund wrote on Mon, 04 April 2011 19:53

That is normal. You can have different behavior depending on teh container easily.

Erik Englund wrote on Mon, 04 April 2011 19:53

Secondly, I get strange behavior whenever I drag a sub library out into the root context. I get two libraries to show up in the root context.

It should be a known bugs: https://bugs.eclipse.org/bugs/show_bug.cgi?id=318585

Regards,

Re: Containers of Contains Behaving Weird [message #663377 is a reply to message #663369]

Mon, 04 April 2011 15:51

Eclipse User

So then I have a question on best practices. How should I go about customizing the behavior of this edit part. Should I use the edit policy extension point to change its behavior. Or should I override the behavior in each of the generated edit parts by marking them generated not.

My big problem is that in my diagram I want to display as root nodes items that are not directly accessible from the root element of the model. Should I do this by providing my own CanonicalEditPolicy?

If so how should I register it. I'd prefer to not have to reference any of the VISUAL_ID generated by the tooling since those could possibly change if my model changes.

Re: Containers of Contains Behaving Weird [message #663385 is a reply to message #663377]

Mon, 04 April 2011 16:03

Eclipse User

Hi,

Erik Englund wrote on Mon, 04 April 2011 21:51

My point of view is:
- NEVER use @generated NOT
- try to use extension points and providers first
- use GMF aspect templates if there are no extension points available or if the modification occured on every elements of your model.

Erik Englund wrote on Mon, 04 April 2011 21:51

My big problem is that in my diagram I want to display as root nodes items that are not directly accessible from the root element of the model. Should I do this by providing my own CanonicalEditPolicy?

not sure, but you can take a look to phantom nodes.

Erik Englund wrote on Mon, 04 April 2011 21:51

If so how should I register it. I'd prefer to not have to reference any of the VISUAL_ID generated by the tooling since those could possibly change if my model changes.

In order to avoid that, you just have to keep the .trace file that is generated.

Regards,

Re: Containers of Contains Behaving Weird [message #663395 is a reply to message #663369]

Mon, 04 April 2011 16:31

Eclipse User

Aurelien Pupier wrote on Mon, 04 April 2011 21:31

Hi,

Erik Englund wrote on Mon, 04 April 2011 19:53

That is normal. You can have different behavior depending on teh container easily.

BTW, there is a feature request to don't have this behavior: https://bugs.eclipse.org/bugs/show_bug.cgi?id=332224

Previous Topic:	Duplicated elements after Drag&Drop to compartment
Next Topic:	the label remains close (attach) the association

Goto Forum:

-=] Back to Top [=-

Current Time: Fri Jul 04 23:45:41 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter