MDG creation

[qwerty]

 Why is it that MDG cooking feels like black magic? You save a couple of profile data to (often) the wrong place and EA stitch these together to a MDG. (Sparx has already seen that this is suboptimal and accepted to work on an improvement.) Then when I load the changed MDG there are just two possibilities. A) it works. B) it has flaws like stereotypes not appearing or toolboxes not being bound to diagrams. One remedy is to carefully re-save all profile data (let`s hope for a soon improvement of this process). But if that was not the cause your are lost. EA simply swallows all diagnostic information while I guess it's available somewhere inside the guts of EA.

The same goes for loading add-ins.

q.

P.S. The reason for writing this post was that a toolbox was not bound to a diagram. Now it looks like that the name is the reason. I called it Requirements and it did not work. After calling it Requirement (without s) it worked. Similarly for Activity. Maybe I did not read the FM carefully. However, why this constraint? My toolbox is inside my MDG. I should be allowed to call it at will.

(Another case for a "solution" 5 minutes after posting. But this time I don't delete the post.)


P.P.S:

toolbox: string = ToolboxName (where ToolboxName is the name of the toolbox profile for the toolbox that opens automatically each time a diagram is opened)

is what the help says. Nothing about any constraints.

So I tried what Override Default Toolboxes tells:

For example, the profile diagram's Notes field could resemble the following:

RedefinedToolbox=UML::Class;Alias=Class;Notes=Structural elements for Class diagrams;

with

RedefinedToolbox=UML::Requirements;Alias=Requirements;Notes=blabla;

again with no success. The default toolbox still looks like the default toolbox.

P.P.S. Not adding insult to injury but the _defaultDiagramType does also not work. At least when you try to add your own diagram types. It goes without saying... The help says:

The following initial values for _defaultDiagramType should be used to refer to Enterprise Architect's inbuilt diagram types:

. If my English is not too bad then should is not must. It's recommended but not mandatory.

[qwerty]

Well ---- here's my "solution". I renamed the toolbox diagram so they distinguish from those of EA by adding a prefix. The Toolbox header in the Diagram Toolbox is correct as it takes its name from the toolbox class. But in the context the toolbox diagram name is taken. EAUI.

q.