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 - Geert Bellekens

Pages: 1 ... 514 515 [516] 517 518

I'm writing a little validation tool that visits (a part of) the model and validates some of our modelling rules against those visited items.
When testing on a local EAP file I got a run time of 7.5 minutes for 10.000 validated items.
When testing on a model on the SQL server I got 46 minutes for the same items.
Does anyone have an idea how I could improve the performance on SQL server repository?



You are looking for the "Assembly Registration Tool" regasm.exe
Look here: for details.


Hold down the control button when dragging the element onto the diagram.
That should make the diagog appear giving you the choice to create a simple link, an instance, or a new child.

Sorry I didn't read your question properly  ::)
I see this is answerred properly now.

Did anyone actually make the feature request to expose the "OpenPropertiesWindow" to the API?
I was just looking for that exact function, but the only thing I found that is somewhat related an "OpenDiagram" and a "ShowInProjectView"



I doubt that this is a licencing issue. I think the EA.Interop.dll is going to be the same for all versions.
What I did notice when we did the upgrade to 7.5 here was that some workstations didn't get the new EA.Interop.dll, so it might be an installation issue.
I would check the version of the files responsible for the API.



I think you should be looking at the IDualDiagram interface.


So how exactly did you solve it?
Have you introduced a sleep() for a few seconds before continuing or...?


I have some experience writing model validation tools, and I doubt this approach will bring you much benefit.
Usually modelling rules are rather complicated, and best expressed in a programming language.
Trying to express those in something like xml will probably give you more headaches then benefit.
Of course you have to make sure that the rule definitions are nicely separated from your visiting code so that you can easily add/change/remove rules without impacting the rest of the application.
(think visitor, strategy)


Automation Interface, Add-Ins and Tools / Re: Attributes to Message
« on: May 14, 2009, 10:26:41 pm »
It is not.
Why in UML's name would you want to attach a message to an attribute?


Update() will save the properties of an object to the database, think name, notes etc..
Refresh() will save the changes made to a collection such as element.attributes.

Usually it is enough to update or refresh after making all the changes to an element, except when creating new elements. Then you need to call update right after you created it (that will give it its ID). Only then you can continue to work with it.

... I think ... :-?


Seems like it is documented since you found it in the ... documentation. ;D
Anyways, it could always be that this first parameter is not used anymore, but the code sample was never adjusted.


Automation Interface, Add-Ins and Tools / Re: Auto layout for diagram
« on: April 16, 2009, 10:00:47 pm »
No, sorry, no experience. I just remembered seeing that function in the documentation.

Automation Interface, Add-Ins and Tools / Re: Auto layout for diagram
« on: April 15, 2009, 11:32:38 pm »
Try Project.LayoutDiagramEx

API docs are in the help (user manual)
Your application should be quite simple.
- Connect to the correct project (this should get you a Repository object)
- get the project interface from the repository
- call Project.RunHTMLReport (string PackageGUID, string ExportPath, string ImageFormat, string Style, string Extension)

I think there are some examples on the website too that show you how to open an EA model using the API.

I don't think so.
If I'm correct the eclipse integration will only allow you to use EA from within Eclipse. So without EA there would not be much to use.

Pages: 1 ... 514 515 [516] 517 518