One vi with multiple windows

[mjbeals]

I want to thank you again for all of your help so far and sticking with me through this.  It's only my first week working with labview....

Anyway, I managed to figure out notifiers, but am having a flow control issue.  My sub vi's make use of event handlers, so when I pass the notification to the VI, these loops never receive it because they are paused.  This is preventing the VI from closing down gracefully.  Is there a way to trigger a custom event?

My second issue may be trivial.  I'm compiling this to run on the runtime.  When I run it in labview, I can open and close the sub vi's through the buttons on the main panel, but when I attempt it with the compiled runtime, nothing happens.   I have a feeling it's something to do with the path definition and how they are being compiled, but I don't even know where to start looking.

thanks again.

[SteveChandler]

See the attached vi for an example of how to use user events.

You do not need to build the called vi into an exe. Even in the runtime you can just call a vi and run it. In fact an exe is just a fancy zipfile containing vis.

If your called vi has subvis you need to create a source distribution in your project so that all the dependancies can be found.

[RavensFan]

---

@mjbeals wrote:

My second issue may be trivial.  I'm compiling this to run on the runtime.  When I run it in labview, I can open and close the sub vi's through the buttons on the main panel, but when I attempt it with the compiled runtime, nothing happens.   I have a feeling it's something to do with the path definition and how they are being compiled, but I don't even know where to start looking.

---

Look at this KB article Why Does My Executable Not Work When Using the Current VI's Path Constant?