for this way I use following: First I'm creating a notifier which i wire into the placed SubVIs. So I know when they have to stopp execution by checking it's avaibility. In the MainVI you can create a loop, which also checks if the notifier is avaible. When you want's to stopp the execution destroy the notifier somewhere (Main or SubVI's) and all other will also stopp.
Hope that helps Henrik
"Elettronica (UK)" schrieb im Newsbeitrag news:email@example.com... > Is it possible to launch several VI's from a parent VI and to still have the > parent running? If so how > > Tom > >
While the "Parent" VI is running, if you programmatically launch another VI (that has front panel), the front panel of the subVI will cover up the parent's... but, if you had other loops on the parent diagram, say that checked for alarm conditions, etc., they would still be running and doing their job.... while the user is now interacting with the front panel of the subVI. A global variable can be used to signal the subVI to exit. When you exit the subVI, the parent's front panel re-appears.
Hope that helps, Bill
Elettronica (UK) wrote in message news:firstname.lastname@example.org... > Is it possible to launch several VI's from a parent VI and to still have the > parent running? If so how > > Tom > >
> Is it possible to launch several VI's from a parent VI and to still have the > parent running? If so how >
Calling a subVI will delay the execution of things that have a dataflow dependency, but not things in parallel. This means that things that do not directly depend on the output of the subVI will continue to execute while the subVI runs.
What happens when the objects are in a loop? A loop diagram cannot begin another iteration until each node in the diagram completes the current iteration. If you do not wish for the nodes to wait on another within a loop, it is best to break them into separate loops that are less dependent on each other. If you need to add communication back, you can do so with occurrences, notifiers, queues, or even local and global v ariables.
Finally, another way to do this with subVIs is to make the call into a VI Server Run method. This has an option to not wait.