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 - Helmut Ortmann

Pages: 1 ... 47 48 [49] 50 51 ... 59
Automation Interface, Add-Ins and Tools / Re: Add-in Error
« on: July 14, 2014, 07:41:20 pm »

I use Visual Studio and I have no problems debugging it. The Express version allows debugging for DLLs only for release 2008. I think there is a patch available to make it work with Visual Studio 2010.


Automation Interface, Add-Ins and Tools / Re: Add-in Error
« on: July 14, 2014, 06:41:18 pm »

I think the problem is somewhere deep in understanding the net framework. The concept of manageable and unmanageable code.

It means: There is manageable code (.net code) and unmanageable code inside your assembly (*.dll).

You may use google to search for:
Mixed mode assembly is  built agains version `v2.0.50727`

In my opinion you use a library which isn't compatible with .net 4. It may be enough to add some configuration information to the code.

May be it's enough to compile it at .net 3.5.


Hi Dan,

diagramlinks you can hide.

In case of diagramobjects you may try it. I'm sure that there is some kind of workaround to visualize filtered out elements.

My be there is someone who have tried it.



you may set the style of a
  • Diagramlink
  • Diagramobject
via API.

As far as I know there is no special API according to diagram filters.



I didn't catch it.

The copied elements have new GUIDs. That's ok and there is now way around it.

What's with the tagged values (type RefGUIDList)? They should be copied without change.  


Automation Interface, Add-Ins and Tools / Re: Deleting diagrams
« on: July 15, 2014, 10:38:40 pm »
Hi Clemo,

diagrams are created and deleted in the context of the owned element. Here: Package or Elements may contain Diagrams. Details see at Attribute Diagrams (collection) in the API object reference.

You can add/delete diagrams on the collection of diagrams in Package or Elements. The command is: Delete(short index) or DeleteAt(shortIndex, refresh).

Thomas Kilians e-book ScriptingEA may be a good help to understand and master the EA API.


Automation Interface, Add-Ins and Tools / Re: Database Sizing
« on: July 14, 2014, 08:23:14 pm »

in my experiences 100MB database size is a good starting point.



sometimes when JScript don't offers a feature which is available in VBScript you can call a VB Script from JScript.

Some times ago I have done it with waiting for a period of time. The example I got somewhere on the internet. You may even dynamically create the VB script and then call it from JScript.

Ok, it might require some digging in the internet.



the following code works in EA JScript:

var txt = Session.Input("Input value");

Session is an Object provided and documented by EA (see Online Help).


Hi Christer,

I think that's just a JScript Problem. With prompt() method it should work.

or other sides.


Automation Interface, Add-Ins and Tools / Re: Tagged Values
« on: July 11, 2014, 11:07:43 pm »
Hi Jon,

as far as I know there are no special integrity rules for Tagged Values implemented in EA.

You may use one of the Events in an Addin to make checks (disconnect, Context Element Changed,..).


Automation Interface, Add-Ins and Tools / Re: Cloning of an element
« on: July 11, 2014, 11:20:18 pm »
Hi Clemo,

the element don't contains any .Clone() method.

Only the package contains a .Clone() method. Because you can only call this method from a package there is no chance to clone an element alone.

You may do the following:
- Create a new empty package
- Move element to empty package
- Clone package
- Move old element back to his old location
- Move/rename cloned element to the wanted location


Automation Interface, Add-Ins and Tools / Re: Cloning of an element
« on: July 11, 2014, 01:09:32 am »
Hi q,

great. There is always something to learn.


Automation Interface, Add-Ins and Tools / Re: Cloning of an element
« on: July 10, 2014, 10:33:40 pm »
Hi Clemo,

you may try export/import via API. It may work but I haven't tried it before.

Cloning a Package don't looks as an easy tasks. There are a lot undocumented features used in EA and it will properly take you some time to get a general clone working.

If you know the possible package content then it might be possible (reducing of complexity to your issue).

Try to search the forum for example Clone.

If you find a solution please post it hear. I think there are some people also interesd in a viable solution.


Automation Interface, Add-Ins and Tools / Re: Cloning of an element
« on: July 10, 2014, 07:21:12 pm »
Hi Clemo,

cloning a package is quite simple.

1. Package Browser
Use Copy and Paste for a package. The package and the nested packages are cloned.

2. Export / Import *.xml
Copy Package (recursive) to XML and import it at another location in the project tree. At start of import don't forget to click on Strip GUID. The result is:
The package is cloned to the new location. Each element is new but has the same features as before.


Pages: 1 ... 47 48 [49] 50 51 ... 59