Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Topics - Paolo F Cantoni

Pages: 1 ... 74 75 [76] 77 78
The EA Help shows how to define a default diagram type for a specific stereotype.

However, the _defaultDiagramType attribute is applied to the metatype, not the stereotype (don't really understand why, perhaps someone could enlighten me).

So how does one make different default diagram types where you have more than one stereotype extending the same metaclass?

Do you create more than one metaclass element (one for each diagram type)?


When you create an MDG, you create profiles which start with «metaclass»(es) which get extended by stereotypes.

One of the available metaclasses is "Classifier".  I believe I understand what it is - it's the base item that "Class" and "Use Case" and "Activity" extend to define themselves  (please correct me if this is not so).

So, what is the function of this item in an MDG?   To allow us to create new types of metaclasses?  For example, I want to create a new type of thing - a Term.  I could extend "Class", but that would create a Class stereotyped «Term».  I'd actually like to create a new type of thing (such as a Requirement or Feature or Change etc).  This is because I want to stereotype Terms (with their own subset of stereotypes).

Can I use the Classifier metaclass for this purpose?  Should I be able to?  It would seem to me that the ability to for users to be able to create new types of elements (like Sparx is able to do would be REALLY REALLY cool...)


Is it possible to stereotype a diagram within an MDG Technology?

I can create a new diagram type.  But I'd also like to set a stereotype.  Is it possible?


Automation Interface, Add-Ins and Tools / VBScript Libraries
« on: February 22, 2010, 06:25:30 pm »
In:  VB scripting problem, Geert Bellekens makes the observation:
I think the message is: only use VBScript for small disposable quickies.
If you want to do anything decent, use a real programming language
I know it is possible to create libraries of VBScript functionality (such as via the use of ExecuteGlobal) but these are cumbersome (and, I suspect, subtle-error prone).

Are there any suggested mechanisms for the creation of such VBScript/JScript libraries or do I just tell my customers - follow Geert's dictum (which I agree with).


Automation Interface, Add-Ins and Tools / Limits on MDG Technologies?
« on: February 04, 2010, 02:57:20 pm »
Elsewhere, the Sparxians have commented that there's effectively no limit on the number of QuickLinker entries one can have.

This topic is about the same question regarding MDG Technologies.

Is there any practical limit to:
  • The number of MDG Technologies that can be specified (available) to an EA instance
  • The subset of the above that can be active enabled at one time?
Assuming there's (effectively) no practical limit (to at least the number that can be specified), should we give free reign to our imaginations and specify pretty granular technologies to allow the modeller to "mix-and-match to their heart's content?


Automation Interface, Add-Ins and Tools / LinkAccess Column - What is it?
« on: February 07, 2010, 05:56:12 pm »
Anyone know (or is prepared to say) what the LinkAccess column of the t_connector table does?


See: Aggregation and Association proposal for a proposal to provide consistent processing and rendering of EA Aggregations, Compositions and Associations.

There are implications for the use of the Automation Interface which you may wish to comment on.


Is there any?  I couldn't see it...

Can anyone point me to it or categorically say it doesn't exist?


Now that you can use either the Swimlanes or Matrix mechanism in your diagrams, can someone point me at the SDK support for the Matrix setup?

diagram.Swimlanes etc is available but I can't se any equivalent for the Matrix tab.

I can see the effects in the DB, but can't figure out how to do it via the SDK.


This is nice functionality, but I couldn't see how to do it by automation.  Is it possible?


Doesn't seem possible...  (as of build 847).

Is that the case?

project.LayoutDiagramEx (string DiagramGUID, long LayoutStyle, long Iterations, long LayerSpacing, long ColumnSpacing, boolean SaveToDiagram)
only  applies to the legacy layout function - Yes?

Any ETA on it?


Automation Interface, Add-Ins and Tools / Changing the Diagram Type
« on: July 17, 2009, 05:07:42 pm »
With the UI, you can change the diagram type.  How can you do it via Automation?  The Attribute is READ-ONLY.


public void SetConnectorCustomProperty(EA.Connector connector, string propertyName, string propertyValue)
    EA.CustomProperty oCustomProperty;
    for (short iCustomerPropertyIterator = 0; iCustomerPropertyIterator < connector.CustomProperties.Count; iCustomerPropertyIterator++)
        oCustomProperty = (EA.CustomProperty)connector.CustomProperties.GetAt(iCustomerPropertyIterator);
        if (oCustomProperty.Name == propertyName)
            oCustomProperty.Value = propertyValue;

Fails when attempting to set the diagram with a (to me) spurious error:
"EA_MenuClick: Element no longer available"

Anyone know how to set Custom Properties for Connectors?


Hi All,

Am I correct in asserting that there is no Automation Interface mechanism to GetPackageByPath?

GetPackageByID and by GetPackageByGUID exist, but there is no way to find a package by its named path (for example: Model::View::Parent::Self)

Similarly, there's no equivalent get Element yes?


Before I send of a bug report to Sparx, I thought I 'd ask the automation gurus if there was any way to completely remove any trace of a newly create (by automation) diagram and then reload it to simulate a manual open/reload of the diagram?

Effectively to flush the diagram from the EA cache!

I have a strong suspicion that something is "hanging around" but I don't know enough about the AI to ensure I've eliminated the diagram.


Pages: 1 ... 74 75 [76] 77 78