Assigning a non-loaded MDG stereotyp

[qwerty]

I just stumbled over a weird behavior (ah, sorry, not for EA where this is normal behavior). I disabled an MDG so only the basic UML was active. Then I manually assigned a sterotype to a class which had the name of the disabled MDG. Say, it were MyProf::test I just assigned test. Funny enough the color of the class changed since MyProf::test had a shape script which obviously was triggered. Looking into t_xref told me that EA indeed assigned MyProf::test to the class. Hmm, cache?

Ok. I removed the stereotype, closed EA with the MDG disabled and restarted it. Assigned the stereotype again and EA again had the FQN  MyProf::test. How? Is it just to early for me? Am I just hallucinating?

q.

P.S. Maybe a hallucination. Tried it once more and now it did not assign the FQN.
P.P.S. No. It's still behaving weird.
P.P.P.S Forgot to mention I tested on V14. V15 is more strict and does not allow to assign "free" stereotypes. At least one fixed issue.

[Geert Bellekens]

Yeah, since probably v14 EA still loads all MDG's, even if they are disabled.
The only way to really get rid of them is to physically delete the files from the program files folder.

I believe the recommended way to handle MDG's is to use perspectives

Geert

[qwerty]

Yeah, that's how it looks like. Unfortunately my customer is forced (by their own rules) to use V14. They'll need a good ralley assistant ;-)

q.