2. I have a broken link between Stereotypes and UML Types (in Settings | UML Types) which also is stuck in the Stereotype-list and so it cannot be removed. (The delete button is disabled when the broken one is selected). I can create a new copy and delete the new one, but not the broken one. This causes two identical Stereotypes to show up when defining Stereotypes in model elements .
Q: How can I remove a broken link between Stereotype & UML Type?
Is one coming from a technology imported into your model? You may not be able to see from that list, but if you look in the resources window and find your technology imported there it may be an answer.
No, it looks good in the resource file (only one instance). Thus the broken fragment seems to be an orphan residing in the database.
I'd be thankful for a script (preferably VBscript) accessing and removing the orphan? (name: "bold.attr" (name doesn't show in the edit fields, see fig 1.) with the erroneous stereotype: "property".
Fig 1: Orphan:

Fig 2: The valid one:

3. For some reason TVs without a value or default value (should be void) suddenly returns the crap value instead of an empty string: "$ea_notes=". TVs with valid values returns its value as expected, only the empty TV values returns this strange crap ("$ea_notes="). This odd "value" started to show up after I had updated the Stereotypes as described in the beginning of this post.
Pretty sure I remember that some tagged value tables in EA don't have a notes field. That identifier was used to separate notes from the value proper. Not sure why it's showing up for you though.
No, nothing there. Preview shows this :
<TaggedValues>
<Tag name="Bold.CPPName" type="Bold.CPPName" default="" values="" unit="" description=""/>
Both "default" and "values" have (proper) empty strings, no crap in them, so either there's a bug in the importer (probably not, because it looks good in the TV editor after import), or (more probable) in the code generator. The code generated result :
"...,Bold.CPPName=$ea_notes=,..."
(the "$ea_notes=" shouldn't there. Expected result should be no value at all).
As you pointed, there is no such thing as a "note" field in the TVs, so one possibility is that someone has planned for a future note field and that that extra note field is referenced, perhaps as an intermediate (extra) Json field when retrieving model element data internally for the code gen?
Hm, isn't there any patches for EA10* fixing this hassle with Stereotypes?
I mean, $699 is pretty much only for fixing that little bug (EA10 Ultimate ->EA11).
No upgrade prices either?
Only the current version will get any fixes. ...
The hassle with stereotypes was discussed here (on the forum) long before EA11 came. I had to abandon my projects then, but now again I have even bigger need for supporting special code generation.
1. Well yes, but if I drag a, say, "<<myAssociation>>" to the diagram, then my new association should also have its Stereotypes set for the association ends to "<<myRole>>", but now the Stereotype fields are empty for the association ends after the association is created.
There's no built-in way to specify that associations with one stereotype should cause their roles to be stereotyped too. Or at least not one that I know of.
OK, I have made a VBscript that iterates the model and inserts stereotypes for roles where they're missing. Is there a way to run scripts automatically at certain UI events or the alike? Or a quick meny for running scripts for "current" model elements?
(continued, post too long)...