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.

Messages - philchudley

Pages: 1 ... 32 33 [34] 35 36 37
ClearCase does indeed offer an SCC client, which can be used for version control, procedures explain very well in Help or User Guide

I know several large organisations in the UK who use both ClearCase and EA successfully



Automation Interface, Add-Ins and Tools / MDG_MDGGetProperty Method
« on: May 21, 2011, 01:06:23 am »
Hi All

I am writing an MDG Add In and all works well so far, however I am having a little trouble in implementing the method MDG_MDGGetProperty which in C# returns an Object type

According to the user guide THREE items have to be returned:

1) IconID (used to change the project browser icon)
2) Language
3) HiddenMenus

The user guide does make it at all clear how these values are to be returned, are they one string and if so how are the values identified?

The skimpy example in the user guide implies THREE returns under the control of if statements, does EA call this event three times?

In addition, is the IconId an actual ico in the sense of an Icon resource in a Visual Studio project?

Any assistance would be gratefully appreciated



Hi all

Does anyone know if it is possible to automate the synchronisation of tagged values held within a UML profile?

The idea is automate the process of opening the resources view, righ-clicking on an element within a UML Profile and selecting Sync Tagged Value and Constraints...

Cannot find any clues within the EA User guide and I am using EA version 8.0 (the latest build)



As far as I aware the parts compartment cannot be shown in EA SysML  >:( (Bizzarly, you used to be able to do it with the old SysML 1.0 Add-in which was not an MDG)

However, what DOES work is setting the stereotype for an attribute in the block to either part (on the stereotype dropdown list) or value (entered manually)

The latter will give you a similar effect to the diagram in your post, but the unit constraints are not shown (not sure how to that in EA) it also shows value and part and not values and parts

You may have to turn on attribute visability for the block (right-click the block and select Feature Visibility)



Automation Interface, Add-Ins and Tools / Re: Package Icon
« on: April 08, 2011, 06:20:26 pm »
Thanks Aaron, I can confirm this as a few hours after the post I discovered this little Gem in the EA user guide under MDG Add-Ins

Didn't think to look their before the post.  ;)



Automation Interface, Add-Ins and Tools / Package Icon
« on: April 07, 2011, 07:15:25 pm »
HI All

I am developing an Add-In which integrates EA with another Tool. I have noticed in the add-ins for DOORS integratation and Visual Studio Integration that when a package is connected to a DOORS server or a Visual Studio Project, then the package icon in the project browser has an addition indcator (or the icon changes)

I need a similar functionality. Changing the Icon for a view is easy, (package flags VICON) but how is it achieved for a package?

I have looked at the underlying database structure, and user guide but no clues?

Any help would be most appreciated



Not that I know off, however if you can live with a stereotype it is very easy to change an elements appearance via tagged values using shapescripts.

Not sure if this of any help, but maybe worth a look



Automation Interface, Add-Ins and Tools / Re: MergeInstructions
« on: February 19, 2011, 03:36:45 am »
I haven't actually performed any automation of baselines, but I have wriiten a number of Add-Ins.

From the EA User Guide the DoBaseLineMerge has the following signature

DoBaselineMerge(string PackageGUID, string Baseline, string MergeInstructions, string ConnectString)

It appears from your post, that you have not specifed the package name, so perhaps (I am guessing), EA tries to achieve a merge using the latest baseline which happens to be identical to the current model?

Although I would have thought that if the signature was incorrect, then the code would not have compiled.

A colleague of mine has automated baseline merges, so I'll dig out his code, and hopefully post a more detailed reply.



Automation Interface, Add-Ins and Tools / Re: Hide Diagram Note Element
« on: January 29, 2011, 02:09:05 am »
Here's my suggestion, assuming you are using version 8

Use diagram filters to elements, this works the opposite way round to your first think!

I am not sure how you add your notes, but the following is how you would hide a Note Element and a Text Element (both added from the Coomon toolbox)

1) Open up the Diagram Filters view
2) Create a filter which selects elements whose object type is One Of every object type EXCEPT NOTE and TEXT
3) Set the Filter option to Hide from the DropDown list
4) Check the filter on, and you should see all the Notes/Text dissapear

Then when you create your documentation the diagram will print without the notes (confirmed by Print Preview)

In step 2), use the ... button to select all element types and then unselect NOTE and TEXT

If you are using just one note type then the filter is just a simple object type not equals

I am not sure if there is an API method to apply an existing filter to a diagram, I cannot locate one in the current user guide

Hope this helps



Many thanks for the replies, I will try these ideas out when I return the office on Monday



Hi All,

How do you remove a connector from an element. I have tried using the Delete and DeleteAt methods followed by a Refresh for the Elements's connectors collection.

Examine the size of the collection confirms that something has in fact been deleted, but examination of the Element's propery dialog Links tab shows the connector to still be there!

It is also present on all diagrams where this element is present.

Do I also have to remove the connector from the Diagram's DiagramLinks collection as well?

The code examples in the User Guide show the creation of a new connector (no diagram is necessary), but do not show the removal of a connector.

Any advice will be most appreciated



Automation Interface, Add-Ins and Tools / Re: Interfaces (IDual vs I)
« on: January 11, 2011, 08:56:30 pm »
Thanks Alistair, that clarifies it for me I use C# and so will continue to use the IDual

Thanks again


Automation Interface, Add-Ins and Tools / Interfaces (IDual vs I)
« on: January 11, 2011, 04:05:52 am »
Hi All

Probably a question directed at the Sparxians, but in the object model API the Interfaces appear to be duplicated, IDualElement, IElement, IDualCollection, ICollection etc

Is there any fundamental difference between the IDual version and the I version?

If not why are both supplied? If there is what is the difference and when should each be used?

If have written Add-ins using IDual and I have written Add-ins using I, and I cannot see any noticable difference

Any thoughts?

Automation Interface, Add-Ins and Tools / Re: requirements trace
« on: December 14, 2010, 03:10:49 am »

Assuming that you wish to start at an element and then identify the requirements realised by an element, then the following would work

public ArrayList getAllRequirements(EA.IDualElement useCase)
            // Get the connectors for this use case
            EA.IDualCollection connectors = useCase.Connectors;

            ArrayList requirements = new ArrayList();

            // iterate the connectors looking for realizations and add the
            // requirement which it is the supplier to the ArrayList

            foreach (EA.IDualConnector connector in connectors)
                if (connector.Type == "Realisation")
                    EA.IDualElement common = currentModel.GetElementByID(connector.SupplierID);
                    if (common.Type == "Requirement")
            return requirements;

Where currentModel is an instance of an EA.Repository class

The above code template could be adapted for, beginning at a Requirements then returning all elements realising that requirement, something, like this:

public ArrayList getAllRealisingElements(EA.IDualElement requirement)
            // Get the connectors for this requirement
            EA.IDualCollection connectors = requirement.Connectors;

            ArrayList realisers = new ArrayList();

            // iterate the connectors looking for realizations and add the
            // element which it is the client to the ArrayList

            foreach (EA.IDualConnector connector in connectors)
                if (connector.Type == "Realisation")
                    EA.IDualElement common = currentModel.GetElementByID(connector.ClientID);
            return requirements;




The query

SELECT DISTINCT ProductName FROM t_datatypes WHERE Type='Code'

works, but only returns a subset of the languages  :-[

That is

Visual Basic

this is despite that fact that I have the Ultimate licence

I have found that the MDG Technologies appear to update the t-datatypes table upon loading, so I would expect to see languages like ADA for example. This is clear from the underlying XML since you can add your own language to the list by using an MDG

So where are these datatypes going?

Pages: 1 ... 32 33 [34] 35 36 37