Clickable links in system output window

[OpenIT Solutions]

Hi,

I'm assuming this is possible - just not sure how. I want to include clickable links (hyperlinks) to model elements and diagrams in the text displayed in the Sparx system output window. Anyone have a VB script example of how to do this ? Any pointers to help/guides ?


Regards,


Jon.

[qwerty]

See the help: WriteOutput (string Name, string Output, long ID)
    ID: Long - specifies a numeric ID value to associate with this output item for further handling by Add-Ins; can be set to 0 if no handling is required

q.

[Geert Bellekens]

I think it works even without specific code. If you pass the ElementID then EA will select that element in the project browser upon doubleclicking.

Geert

[niko_ea]

Hi,

I understand this topic is almost 7 years old, but I am experiencing the same issue and haven't been able to resolve it with the existing recommendations. Unfortunately, when I use the Repository.WriteOutput() method in my Add-In and pass the ElementID, EA does not select the element in the project browser upon double-clicking.

In my Add-In, I have various checks that print warnings in a separate tab in the System Output window. For example, one of the checks prints a warning if an element has no connections, like this:
"The element ... has no connections."

What I want to achieve is to either print the element as a hyperlink, similar to how it can be done in the notes, or allow the user to click the OutputItem and be redirected to the element. Unfortunately, I am not sure how to do this.

I would greatly appreciate any suggestions. Thank you very much in advance for your help.

Best regards,
Niko

[Geert Bellekens]

You have to implement the events
- EA_OnOutputItemDoubleClicked
https://sparxsystems.com/enterprise_architect_user_guide/16.1/add-ins___scripting/ea_onoutputitemdoubleclicked.html

or
- EA_OnOutputItemClicked https://sparxsystems.com/enterprise_architect_user_guide/16.1/add-ins___scripting/ea_onoutputitemclicked.html

Geert

[niko_ea]

Thank you very much! Calling Repository.ShowInProjectView() in one of the two functions works as expected!