MDG _subtypeProperty to support multiple tagged values

[Guillaume]

Hi,

I used while ago the _subtypeProperty attribute in my MDG UML profil to prompt the user to select an enum tagged value when creating the stereotyped element.
This is used for instance in the built-in BPMN MDG on tasks and gateways.

I have a stereotype that uses 2 enum tagged values and it would be great to be able to provide both tagged values in _subtypeProperty  so the user is prompted to select the values for each tag.

Similarly, could there be a way to specify in the toolbox the default values to set on a stereotyped element's tagged values?

[Eve]

I used while ago the _subtypeProperty attribute in my MDG UML profil to prompt the user to select an enum tagged value when creating the stereotyped element.
This is used for instance in the built-in BPMN MDG on tasks and gateways.

I have a stereotype that uses 2 enum tagged values and it would be great to be able to provide both tagged values in _subtypeProperty  so the user is prompted to select the values for each tag.

I can't think of a way to do this that wouldn't be a horrible user experience. Is it really two types or just something that you want the user to fill in? I would probably just go for a shape script that makes it clear that it's incomplete. Options include a dashed border on the basic shape or a great big red bar across it.

Similarly, could there be a way to specify in the toolbox the default values to set on a stereotyped element's tagged values?

There is an existing mechanism for this. Create a pattern and then use UMLPatternSilent on your toolbox.

[Guillaume]

Hi Eve,

I did a few tests on integrating silent patterns in the toolbox and it seems to be a valid alternative/solution to what I was looking for.

Thanks 
Guillaume

[Guillaume]

Hi,

I noticed that using patterns within a toolbox doesn't support an incremented number on the new elements' names.
For instance I always get the name as set in the pattern e.g. CustomClass, whereas users would like to have CustomClass1, CustomClass2, etc.
Is there a way to achieve this?

Thanks

[qwerty]

I wonder which user ever wants their classes numbered rather than named meaningful.

q.