06-17-2014 10:07 AM
There are some good shipping examples that help explain the Asynchronous call by reference functions too.
06-18-2014 04:33 AM - edited 06-18-2014 04:50 AM
Thank you.
Another question abaout reentrant-vi.
My dummy-construction with dummy-vis is now working.
Later i want to replace the dummy-vi with instrument-control-vis.
So i will have one vi setup as reentrant that contains three other vis (config, measure, read)
-->Do i have to setup ALL subvis also as reentrant or are they automatically reentrant if the are called by a reentrant vi?
And do i have to close the references created by the "Opne Vi Reference?
Thx
06-18-2014 05:13 AM
You can mix reentrancy without problems, just be wary of the effects of your choice ... Reentrancy isn't inherited. A config-vi can be reentrant if the settings are permanent or handled in other manners, as configuring a com-port. Once it's set it's "permanent" and you can happily set other ports simultaneously, thus a decent candidate for reentrancy.
Some information is unique to the instance, so it might "disappear" if spawning new ones, the simple solution to this is to send all data needed as inputs.
Stuff like that.
/Y
06-18-2014 06:29 AM