tagged value limitations and inconsistencies

[Andrew Warner]

Hi all,
I've been struggling with some tagged value issues. It is in two parts.

Part I
I am using the built in GUIElement types on User Interface diagrams to build UI mockups. I need to add some tagged values to indicate for example the data type associated with the GUIElement.

I can't do this in a proper graphical MDG profile since I don't "own" the GUIElement types. But, I can create the tagged values in the tagged value editor and include them as reference data in the profile.

Now, I have copious numbers of GUIElements existing in the model and want to apply the tagged values to them. Is it possible? The only way seems to be to synchronise using the toolbox stereotypes but that only seems to work for tagged values created as attributes on stereotype element in an MDG profile.

I also need to have the tags applied to new GUIElements. The only way I've found to do that (given that I can't put them in my profile) is using diagram templates. That only applies them to elements that are added to a diagram of that type. It doesn't work if you just use Add->AddElement... to add an element to the project but not to a diagram. Or, presumably, to a diagram of a type that's not in the template directory.

Part II
I am also adding tagged values to stereotypes I do own. That is, in my own profiles. The issue here is that I can't create a tagged value with a type of memo using the graphical profiles.

I can do it using the tagged value editor and reference data but then I can't synchronise for the stereotype to apply it to existing elements or if there's a change in the tagged value.

This effectively puts a limit of 255 chars on any tagged value created and managed in a lovely, standard, conforming MDG profile.

Over to you...
Cheers,
Andrew.

[Geert Bellekens]

Andrew,

I had the same issue, but I "solved" it by running a small program to add the required tagged values to my elements.
Not the most elegant solution, and I need to run this on a regular bases for new elements, but it's "good enough" for me.
I guess you could also do something with an addin in the post_xxx events fired by EA.

Geert

[Paolo F Cantoni]

Andrew,

create a formal bug report/feature request for each problem and post the exact name(s) you used here.  We fellow users can then support your request by submitting the same named report to Sparx.

This is apparently the way they want it to work (although as Geert suggested in Aggregation and Association proposal: PS. This is really a retarded way of voting for features. )

Paolo