Creating DiagramHyperlink via Automation Interface

[Volchik]

Could someone help with example of creating and placing Diagram hyperlink to diagram via Automation Interface.

Simply i have to automate tasks described in "Creating Hyperlinks between diagrams" topic of this help page:

http://www.sparxsystems.com.au/EAUserGuide/hyperlinks.htm

[«Midnight»]

I can find no way of actually creating a hyperlink through automation.

This is a special type of Text element - so far so good. When you try to change it into a hyperlink you have to modify one of the database fields. It is read-only to the API.

Look up which field it is - I don't have it in front of me now, and you'll need the schema open when you do the rest of this anyway.

Now open a 'back channel' to the database via OLE DB. When you've added the Text element to the diagram, tweak the database. You may have to reload the diagram - even if you don't have it visible on the desktop.

David

[Volchik]

Oops
Sad unexpectedness.

Thx anyway.

[Volchik]

Not all too bad.

There is method Execute in Repository interface so i have no need to open 'back channel'.

The field are named PDATA1 in table t_object if someone wants to know.

The problem is solved. Thx.

[Jude Ambrose]

HELLO ALL,

I am still not able to create a hyperlink via Automation.

@Midnight - I agree that its of ObjecType - Text. And also noticed that there is some change ni the PDATA. I dont know what exactly is PDATA? I queried the database and found the value of PDATA is 129 of the hypelinked object on the diagram.

Can anybody help with some sample code for the Hypelink creation by automation?

Best Regards,
Jude

[«Midnight»]

The PDATA columns are available through the API via the MiscData fields. Unfortunately these are read-only fields as you can see in the documentation.

That does not (always) mean you cannot use the API to manipulate the contents of these columns, just that you cannot do so directly. Many of the other API settings and methods cause EA to set values in these columns.

The nice thing about this is that EA does all the work to make sure that the (entire) content of the columns are correct. The downsides are pretty severe though. Among the more obvious are that these columns remain 'magic' in the sense that they are undocumented; they are subject to change at any time, even between versions. Another is that not all the values can be changed via the API (at least not the published parts).

The limitation regarding hyperlinks was one I brought up with Sparx long ago, in EA 6.x days. Perhaps you should raise a formal feature request with Sparx now. If more people do so then the priority of this request might rise to the point where it is acted on.

Use the Feature Request link below the Support link near the Bottom of any forum page.

NOTE: For all I know there could be a way to do this, but it needs to be documented. [And we in the user community need to be told; this forum would be the right place.] IMHO that would be a satisfactory outcome.

[Jude Ambrose]

hey midnight,

Thanx a lot for the brief reply. Will defintiely do a feature request.

cheers,
Jude

[Paolo F Cantoni]

hey midnight,

Thanx a lot for the brief reply. Will definitely do a feature request.

cheers,
Jude

Hi Jude,  please confirm the request was formally made.  I need this functionality tomorrow!    You should point Sparx at this Topic so that they can be aware of any discussion and can also participate.

Paolo