clone vi

[lavalava]

Guys,

Quick question, how do you clone a VI?  I just download an example but I'm not sure how this guy did it... 

[lavalava]

[lavalava]

I've noticed that if I hit ctrl+m, it loses all clone mode but how do I get back to clone mode or vice versa?

[Ben · Accepted solution]

VI properties >>> Execution

Set VI as re-entrant.

Ben

[lavalava]

the file was set as "re-entrant" but if I drag and drop this file into another VI, it doesn't show up as clone.  How should I go about doing it?  thanks

[altenbach]

The relevant LabVIEW help entry.

A description of the new feature. (When it was introduced in LabVIEW 8.0)

ctrl+M switches between run mode and edit mode, that's why things change.

An earlier discussion.

[lavalava]

i've read those threads before I post this one, all I want to do is create a clone.  After I set my VI to re-entrant, I drag and drop this file into another file and it still would not show up as a clone.  How can I insert a re-entrant file as a clone?

[lavalava]

ok I got it thanks guys

[cuthbert]

I have a strange thing happening that is because I have a cloned VI on my block diagram. After using CTRL-M to disable the cloning and getting a non-rentrant VI, I then save the non-reentrant VI in a folder so that I can access the VI. And when I open the saved VI it is in the non-reentrant mode!  However when I go back into the original VI that uses this cloned VI and replace the cloned VI with the non-cloned VI and then open it up I get the expected results where I can actually change the code in this VI. I have actually gone into the replaced reentrant version of the original cloned VI on the block diagram and then replaced the VI witht the saved non-reentrant version of the VI and changed the code in the VI and then saved it again.  Then I reopened the VI and looked the block diagram and the thing was still in the non-reentrant mode. However, When I saved the main VI the non-reentrant VI again became cloned as a reentrant version!  This seems to me to be really strange and I am at a loss to reason this out!  Can anyone explain this behavior?

[RavensFan]

You are confusing terminology.

CTRL-M doesn't change a VI from reentrant to non-reentrant or enable/disable cloning.  You don't "enable/disable" cloning.

Reentrancy is a property defined under the File / VI properties/ Execution menu.  Ctrl-M changes the appearance of a VI from edit mode (what you normally see) to run mode (what you see if the VI is running.)  It will also allow a copy of a reentrant VI that is open (a "Clone") to open up the real, original copy of the VI so you can do editing on it.

A VI that is non-reentrant means there is only ever a single copy of the VI that is running at any given time.  If you try to call a non-reentrant VI from multiple places at the same time, each subVI instance has to wait until the other subVI instances have stopped using it.  With a reentrant VI, a copy of the VI is made when it is called (the "clone").  That means more than one copy of the same subVI can run at the same time, each with its own memory space.