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 - Simon M

Pages: 1 ... 391 392 [393] 394 395 ... 431
They are currently only accessible via the EXEC_ADD_IN call.

At a glance I see your custom list contains only a single underscore.  They actually use a double underscore.

Actually, Element.Diagrams is the list of diagrams owned by the element.  Not the list of diagrams it appears on.

Currently a sql query would be the only way to check for an element being orphaned (that I can think of) but an Element.Usage collection is one of a big list of additions to the automation interface that I plan to push for when I get the time to do it.

Automation Interface, Add-Ins and Tools / Re: Generate DDL via SDK
« on: March 12, 2010, 09:30:57 am »
I've very sorry to say that:
a) DDL generation is not driven by code templates.
b) Unless I'm mistaken you can't perform it from the API.

Automation Interface, Add-Ins and Tools / Re: Code Template
« on: February 22, 2010, 08:31:27 am »
You can't access attributes of a return type from the code template editor directly.  If you need to do that you'll need to use an add-in call.  Do a search for EXEC_ADD_IN for examples.

%dl% -

Automation Interface, Add-Ins and Tools / Re: object types
« on: February 26, 2010, 10:09:24 am »
GetElementByID will always return an otElement.
GetPackageByID will always return otPackage.

Functions that get current context or similar things can return one of the different types.


Automation Interface, Add-Ins and Tools / Re: Project Class Diagram
« on: February 15, 2010, 08:47:57 am »
You're not missing an EA feature.  It does not create a single diagram for an entire application.  In any real world example this will be too large to benefit anyone.

Instead I would recommend making use of your knowledge of the product, and some of EA's features to make more useful diagrams.

For example:

The hierarchy view shows you multiple levels of relationships for the currently selected class. The relationships window shows more information about each of the direct relationships to the current class, and also allows you to drop the objects onto the diagram. Finally, the Insert Related command (in the context menu of an object on a diagram) allows you to insert many related objects all at once.

So, with appropriate use of known significant objects you should be able to achieve some more useful diagrams.

Look for parentedge in the help file.  It doesn't say what the possible values are, but you can work it out fairly quickly by printing it and then moving a port around.

I think you need to look in MiscData(0).

Edit: Thank you to KP for the correction the MiscData is zero based.

Well, the files themselves may be old.  They would only be updated when something new is added to the automation interface.

The build number is available from Repository.LibraryVersion.

The version 8.0 version of the API changes this behavior.  If you can't or don't want to upgrade you can add a check that parentid is zero.

Automation Interface, Add-Ins and Tools / Re: Limits on MDG Technologies?
« on: February 08, 2010, 08:29:56 am »
The help file has this to say about it.

You can make an MDG Technology the default interface to Enterprise Architect. Depending on the MDG Technology selected, this can change the way Enterprise Architect windows are displayed and override the Enterprise Architect UML Toolbox pages with pages specific to that Technology.

Automation Interface, Add-Ins and Tools / Re: Limits on MDG Technologies?
« on: February 05, 2010, 08:50:40 am »
I'm not aware of any limitations.  I am currently running with 36 enabled technologies providing a mix of code engineering, profiles, patterns, searches and rtf report templates.

(With the terminology on the MDG technologies dialog only 1 can be active at a time, but as many as you like can be enabled.)

Pages: 1 ... 391 392 [393] 394 395 ... 431