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 ... 31 32 [33] 34 35 ... 38
What a timely post. I have experience exactly the same thing, I had set to server timout to 60 secs to get an uninterrupted add to version control.

It appears that the lengthy operation only happens on the [highlight]initial configure package[/highlight] or [highlight]add branch to version control [/highlight]operations.

Once added, subsequent check-out, and check-in operate as normal.

Have tried, with and without Torstoise SVN to create the working folder, have tried Collabnet SVN and VisualCVN and all combinations exhibit this initial very long configuration.

I would be very interested to hear other users views


Couple of questions

The information regarding this MDG state

[highlight]providing significant interoperability enhancements for Microsoft's Team Foundation Server.[/highlight]

However all the documentation I have (either Help menu) or PDF user guide provides minimal or non-existent information in this area.

I would expect to be able to connect to a TFS serrver without connecting a VS solution, since all I wish to do is integrated Work / Task items etc ... however I cannot discover how to do this or even it is possible!

I am using the latest version of the MDG, version 4.5.1

Any advice would be most appreciated



Automation Interface, Add-Ins and Tools / Re: RedefinedToolbox
« on: April 18, 2012, 02:08:22 am »
Thanks Graham!

I have now got it to work. Stupid mistake I made which I spotted following your steps.

I had originally saved the profile package containing the ToolBox profile as a UML profile and not the diagram!

I saved the diagram as a profile and now all works as expected.

Thanks again for pointing me in right direction.

Automation Interface, Add-Ins and Tools / Re: RedefinedToolbox
« on: April 18, 2012, 01:55:19 am »
Yes I have three such Stereotypes, and the toolbox appears as expected when it is selected using More Tools...

I just cannot get it to override the default UML Use Case toolbox when a UML use case diagram is opened.


Automation Interface, Add-Ins and Tools / RedefinedToolbox
« on: April 18, 2012, 12:29:05 am »
Hi All,

In the EA user guide (I am using version 9.3 build 931), it states:

[highlight]To replace one of Enterprise Architect's default Toolboxes with one of your own (for example, if you have your
own version of the UML::Class Toolbox that you want to be opened every time a Class diagram is opened -
as long as your technology is active) then include a RedefinedToolbox clause in the Notes field for the
diagram properties of your ToolboxProfile diagram.
For example, the profile diagram's Notes field could resemble the following:
Re d e f i n e d To o l b o x =UML : : Cl a s s ; Al i a s =Cl a s s ; No t e s =St r u c t u r a l e l eme n t s f o r
Cl a s s d i a g r ams ;[/highlight]

I have created an MDG technology with a toolbox profile. On the Notes field for the Toolbox Profile diagram I have the following:

[highlight]RedefinedToolbox=UML::UseCase;Alias=Cambridge Assessment;Notes=Elements for Cambridge Assessment Requirements Modelling;[/highlight]

However, when a Use Case diagram is opened, the default toolbox appears and not my Defined Toolbox as in the RedefinedToolbox clause.

Anyone else experience the same? Have I done anything wrong? My MDG is certainly active.



The diagramID will be null if there is no diagram open when your add-in runs.

Open a diagram, then run your add-in.

... also as KP suggested, test for null before using the returned value.

maindiagram = repository.GetCurrentDiagram(); //recupero del diagramma
if (mainDiagram != null) {
     this.diagramId = maindiagram.DiagramID; //identificativo del diagramma

Just curious, I use Visual Studio 2010 for my development. What version of .NET do you guys use for writing your add-ins, and does it really matter?

I am more curious as to whether you use .NET 3.5 or .NET 4.0 and which would be more suitable for commercial deployment


Automation Interface, Add-Ins and Tools / Re: MDG Technologies
« on: April 06, 2012, 10:10:56 am »
Follow up, I have just conducted a simple test and what I described in the previous post does indeed work as described.



Automation Interface, Add-Ins and Tools / Re: MDG Technologies
« on: April 06, 2012, 09:57:20 am »

What I would try is to create a UML profile where a stereotype that extends the metaclass operation is created.

As usual attributes added to the stereotype will become tagged values for the operation.
You should be able to add the operation, change its stereotype and then the tagged values will be there.

It worked for me for attributes, so I see no reason why it should not work for operations although I haven;t tried it.

Add the profile to the MDG in the usual manner.

Hope this helps



Hi Guys

I like a challenge  :)

After a a bit of playing around, one possible solution is

1) Obtain the messages in sequence order [highlight](t_connector.SeqNo[/highlight])
2) Iterate the messages
3) Obtain the end object id ([highlight]t_connector.End_object_ID[/highlight]) let's call it [highlight]END[/highlight]
4) The calls for the current message will be the following messages where it's [highlight]t_connector.Start_object_ID = END[/highlight]

The process above could then be repeated for each call identified or indeed made recursive

Hope this makes some sense



Automation Interface, Add-Ins and Tools / Re: EA_GetMenuState In EA 9.1
« on: September 15, 2011, 01:07:26 am »
Yes I can concur I get exactly the same behaviour, the menu items for an add-in should enable/disable in the same irrespective of where the menu option is selected. This used to be the case.

I have used the selection of an item in the Project Browser to control add-in menus items many times, and in my latest ad-in more users are likely to be using the add-in menu by right-clicking an item in the project browser.

This inconsistency is both suprising and annoying!  >:(



Automation Interface, Add-Ins and Tools / Re: Where is StereotypeEx held?
« on: October 12, 2011, 02:01:27 am »
It's OK guys, I've found it!

Just for your information, it's buried away in the Description field for the t_xref table.



Automation Interface, Add-Ins and Tools / Where is StereotypeEx held?
« on: October 12, 2011, 01:23:17 am »
Hi All

There is an API functional called StereotypeEx which returns all applied stereotypes for an Element, Connector etc

But where is this information held in the underlying repository? I have a need to extract this information using a SQL query, particularly the StereotypeEX for a connector

It is not in the t_object t_connector tables not can I find in t_xref, it must be somewhere!

Any help most appreciated.

Cheers Phil

As far as I know, and as far as I can discover this information is not available in the API.

However it can be discovered with a little work, well at least in .Net is can

Here is a one line pice of C# .net code

string licenceFilePath = Application.UserAppDataPath;[/b]

The contents of licenceFilePath for my installation running Windows 7 is

C:\Users\pchudley\AppData\Roaming\Sparx Systems Pty Ltd\Enterprise Architect 9\9, 0, 0, 908

If I change version of EA to say Version 8, the same line of code yields

C:\Users\pchudley\AppData\Roaming\Sparx Systems Pty Ltd\Enterprise Architect 8\8, 0, 0, 864

Split the string using \ as the delimiter and the last entry in the string [] will contain (for the first example) 9, 0, 0, 908

That is the version and build number of the EA version that is running your add-in.

Hope this helps in some way.



Right-click the element
Select Advanced from the context menu
Select Make Composite from the flyout menu



Pages: 1 ... 31 32 [33] 34 35 ... 38