[news.eclipse.modeling.gmf] Re: Top Nodes with same class Element - no d

[Aurelien Pupier <aurelien.pupier@xxxxxxxxx>]

Alex Shatalin a Ãcrit :
> Hello Aurelien,
>
> > How I do that :
> > - one top node for each "profile" with different "feature seq
> > initializer"
> In addition to "feature sequence initializer" you have to add 
> corresponding Constraints. This is important to let GMF diagram updater 
> determine how to represent particular domain model element. E.G.:
> - two node mappings referencing same metaclass with feature initializers 
> 1. featureA -> value1 2. featureA->value2
>
> In this case we have to create two constraints featureA = value1 / 
> featureA = value2 for each of NodeMappings in accordance.
>
> -----------------
> Alex Shatalin

doesn't work so fine finally...

The problem is that featureA after being initialized can switch from value1 to value2... Or I have the constraint for 
the top node, so it disappears...

In addition, I want to have multiple initializers so, multiple values and so a lot of duplicate code. (if it was only 
generated code which was duplicated it wouldn't be so annoying but I customise display with another XXXeditPartProvider)


So is there another way to propose different initialization to the user?
Adding a menu item directly in the pop-up menu of creation?
other...