Get VI Icon and Terminals Like in Context Help but in Runtime Engine

[7Ronin]

Hello,

I would like to be able to obtain an image of the VI Icon and Terminals like you see in context help:

But in the Runtime Environment.  I have a architecture that is designed to sequence steps of VIs and I would like to be able to show the Icon and Terminals (like context help or what TestStand shows) but I need to be able to do this in the RTE for security reasons and to ensure users can't tamper with anything by not opening anything in the dev environment.  The available options of invoke nodes to print VI docs to HTML and VI scripting are not supported in the RTE.

Anyone know of a way to get this info?  

[paul_cardinale · Accepted solution]

---

@7Ronin wrote:

Hello,

I would like to be able to obtain an image of the VI Icon and Terminals like you see in context help:

But in the Runtime Environment.  I have a architecture that is designed to sequence steps of VIs and I would like to be able to show the Icon and Terminals (like context help or what TestStand shows) but I need to be able to do this in the RTE for security reasons and to ensure users can't tamper with anything by not opening anything in the dev environment.  The available options of invoke nodes to print VI docs to HTML and VI scripting are not supported in the RTE.

Anyone know of a way to get this info?  

---

Like this.

[7Ronin]

Not Exactly....

The image I need is the one you would get if you were viewing the context help for a VI, that is the icon image and the terminals.

Also, I can't use scripting as this needs to work in the runtime environment. 

Appreciate the suggestion though!

[Darren]

As far as I know this functionality is not available in the LabVIEW run-time engine.

[paul_cardinale]

---

@7Ronin wrote:

Not Exactly....

The image I need is the one you would get if you were viewing the context help for a VI, that is the icon image and the terminals.

Also, I can't use scripting as this needs to work in the runtime environment. 

Appreciate the suggestion though!

---

1. When I run it, I get the icon image and the terminals.
2. I tried compiling to to a .exe, and it still worked.

[7Ronin]

Paul,

That is great!  I honestly did not even attempt an .exe using the scripting node.  I'll see if I can get that incorporated into the plug ins for the sequencing system.

Again, I appreciate you taking the time to respond- much appreciated.

[7Ronin]

Darren,

Paul has found an answer that works, and I'll go with it if there are no alternatives to attempting to use VI scripting in the Runtime Environment.  Are you aware of any alternatives?

Does that information get stripped out of compiled VIs?  The reason I'm asking is my architecture is based on your Multiple Interacting Executables post from a few years ago.  The sequencing engine is actually the only executable and the steps are loaded as uncompiled VI through VI Server calls which is working very nicely and allows compiling only the sequencer, having only the RTE on the customers machines but still not having to go through the effort of PPLs.

Thanks!

[Darren]

---

@7Ronin wrote:

Paul has found an answer that works, and I'll go with it if there are no alternatives to attempting to use VI scripting in the Runtime Environment.  Are you aware of any alternatives?

Does that information get stripped out of compiled VIs? 

---

The only alternative I know of is the full-featured run-time engine, which is only a feature you can use with the LabVIEW DSC Module. I don't recommend going this route.

If by "information" you're referring to things like control descriptions, icons, etc., I don't think control descriptions are removed (since you can view those via the context help in a running EXE), but I don't know off-hand if icons or VI descriptions are removed.

[7Ronin]

---

@paul_cardinale wrote:

---

@7Ronin wrote:

Not Exactly....

The image I need is the one you would get if you were viewing the context help for a VI, that is the icon image and the terminals.

Also, I can't use scripting as this needs to work in the runtime environment. 

Appreciate the suggestion though!

---

1. When I run it, I get the icon image and the terminals.
2. I tried compiling to to a .exe, and it still worked.

---

Sorry, I have to circle back to this.  What version of LabVIEW are you using?  I only get the icon terminal?????