LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Dynamically calling a subvi does not work in executable

Solved!
Go to solution

@rolfk wrote:

@paul_cardinale wrote:

@GerdW wrote:

Hi Matthisc,

 

use a static VI reference and your problems are gone:

You don't even need to include the subVI as "Always included" when you build an executable anymore!


That's worse than just running the sub VI directly.


Actually it's not the same! A subVI runs once when called. This starts the VI and lets it run as its own top level VI until it decides to close. However I would nowadays use Start Asynchonous Call for that! And let the VI open itself when it deems that necessary, not before it is started.


Except that you've wired 'TRUE' to the "Wait Until Done" input.

"If you weren't supposed to push it, it wouldn't be a button."
0 Kudos
Message 11 of 11
(314 Views)