Linking memory

[jyang72211]

For example, you have 1000 vi, and they all contain the same subvi.  You change the name of the subvi.  When you open the 1000 vi, it will ask you for the subvi.  You would have to browse for the same subvi 1000 times.  It labview remember the location of the subvi after you fix the broken link once.  That would save a lot of time. 

[RavensFan]

Are these 1000 VI's you are opening one at a time?

I've never had LabVIEW ask for a particular VI more than once.  Once the subVI is loaded into memory, then the other VI's that you open will use that.

[crossrulz]

Right now if you rename a subVI inside of a project, all of the other VIs in the project will be prompted to save.

[AristosQueue (NI)]

As Ravens Fan points out, LabVIEW does remember the substitution, for a given load of a VI Hierarchy. If your thousand VIs are in different hierarchies, each loading one-by-one, that's when we have to ask every time. Suggesting that LabVIEW remember that substitution permanently creates a problem -- many times the rename is being done in order to remove a name conflict. If LabVIEW just permanently held that name association, then when a VI loaded that you wanted to keep linked to the old name, it would also get renamed.

I think what you're suggesting would require a fairly sophisticated name mapping tool, with dialogs about "would you like me to apply this change now?" popping up during load.

The best existing solution is to just use a project. Many of the rename issues are solved working in that environment. Do you use that?

[tst]

Also, even if the calling VIs aren't in memory at the same time, you can always open them later, do a Find All Instances on the subVI and then replace all the instances with the new VI. I haven't checked if this works when a VI is missing, but it might.

[Darren]

Any idea that has received less than 3 kudos within 3 years after posting will be automatically declined.