How to show screen on loaded VIT

[t_houston]

I have an app that fires off a couple of VIT's.  In normal development mode, the VIT's show up on the screen when called and that is what I want. 

Once I compile the app, the VIT's no longer show up.

I see where it says it won't show up, but is there a method by which I can make it display?  I want them as stand alone windows as in the development mode for a reason and I am not interested in having the screen show up in the calling program.

[nathand]

---

t_houston wrote:

I see where it says it won't show up, but is there a method by which I can make it display?  I want them as stand alone windows as in the development mode for a reason and I am not interested in having the screen show up in the calling program.

---

What are you trying to say with that first question?

Are you including the VITs in the build specification, and is the executable able to find them properly?  Paths are sometimes different in executables than in the development environment, and your screen show doesn't show how you're generating the path to the VIT.  Also in the build specification, make sure you specifically set the properties for the VIT so that compiling does not remove the front panel (the default build setting for most VIs is to remove the front panel, unless it's the startup VI).

[crossrulz]

Why use VI Templates?  Reentrant VIs would be much more efficient.

[t_houston]

I will have many simultaneous VIT's working on data from different sources. 

[t_houston]

You might be onto something.  The VIT's are listed in the compile and are at the same directory level as the top VI.

[t_houston]

This app will be called from a network drive, by many computers.  Any hint on how to correctly refer to the VIT so it can be called.

[nathand]

Do you know that the VIT is currently being launched, but not visible?  Do you do anything with the error wire coming out of Open VI Reference and being passed through the invoke nodes?  If not, you might throw a simple error handler on the end so you'll at least get a dialog if an error occurs, which would help determine the problem.

[t_houston]

You are correct.  It appears that the VIT is not actually getting launched.  I didn't build an error trap since it worked on the development system.  My Bad.