LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Call Options / Reentrant

I have a slight concern with a VI that's called many times as a GUI, but only one instance at the time. When i open the first instance it works properly and then i close that and open the next and my event procedure doesn't work. Few options that i'm concidering and what is the advantage of these.

To make VI reentrant.
To load VI for every call.

Or should my program work without these adjustments.

Message Edited by Englund on 07-30-2007 01:37 PM

0 Kudos
Message 1 of 5
(3,022 Views)

Message Edited by Englund on 07-30-2007 01:37 PM

Message Edited by Englund on 07-30-2007 01:37 PM

0 Kudos
Message 2 of 5
(3,022 Views)

Hi Englund,

Please post some code that demonstrates what you have tried that,

works

and

does not work

This will help us help you!

Just trying to help,

Ben

Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
0 Kudos
Message 3 of 5
(3,006 Views)

Also,

can you define: being called multiple times..  ?

Do you mean they are running simultaneously in parallel (at the same time / or can run at the same time)?

or do you mean called multiple times as being in a loop, so called consecutively? (a number of times, but never at the same time)..

 

The way I read the following: "I have a slight concern with a VI that's called many times as a GUI, but only one instance at the time. ", it sounds like the VI does not execute multiple times simultaneously..  Thus I agree with Ben asking, what works and what does not work??

Message Edited by JoeLabView on 07-30-2007 10:28 AM

0 Kudos
Message 4 of 5
(3,000 Views)
I mean called multiple times, consecutively, never at the same time. It's makes modifying easier if the VI's aren't reentrant (just double click). Reentrant works.
I was just curious about the memory handling of VIs that aren't reentrant and are called multiple times and how they should be loaded into the memory (same time with caller, every time called, third option that i don't remember)

I know what solution work, but i would be interested in how a VI that's called many times with "different" data is processed in the memory, which is not set to reentrant. All the data that is in one instance should be "erased" from the memory when a VI is closed, if i have understood the memory handling correctly.
0 Kudos
Message 5 of 5
(2,978 Views)