How should autopopulating folders handle this situation?

[Aristos Queue]

A logical impasse exists between two highly praised LV features: the autopopulating folders in the project and the cross-link detection/resolution tools. Both of these came into existence in LV8.5.

(Author's Note: I should mention that both of these features are highly praised by people who only use VIs, not by people who use both VIs and libraries, but we're working on that...)

Situation:

Alpha.vi and Beta.vi both call Gamma.vi as a subVI. Alpha wants to load c:\Gamma.vi and Beta.vi wants to load d:\Gamma.vi. The conflict is between two VIs of exactly the same name but at different paths being listed as part of the project. The user needs to either pick which Gamma.vi to use in the project OR remove all references to all but one version of Gamma.vi, making that one the only version of Gamma.vi listed in the project.

The trouble arises when the user tries to pick which Gamma.vi to use. Suppose that the project has an autopopulating folder for c:\, but the user says "Use d:\Gamma.vi for this project." (This reportedly happens somewhat commonly.) The project cannot get rid of c:\Gamma.vi because the file is in the autopopulating folder and the project has been told to keep everything in that folder up-to-date.

And so, with this in mind... please answer the questions.

[Yair]

This poll kinda feels like a "choose your own adventure" book. :laugh:

Personally, I see the moving and renaming options as being the same thing and if possible you should probably unify them to simplify the poll.

[Tomi Maila]

What if we have two versions of a VI both in autopopulating folder. Say I'm using version control on a autopopulating folder. The version control creates a copy of everything and places them by default into a hidden folder. However I decide to configure the version control to place the files under version control into a _xxx subfolder instead of hidden folder. LabVIEW project is opened and voila, both the _xxx version and the normal version of the whole project is within the project. How do you resolve the conflics if you cannot turn off the autopopulating folder when resolving conflicts? Not only every referenced VI has two versions but also every referring VI has two versions.

[Aristos Queue]

QUOTE (Tomi Maila @ Jan 7 2009, 01:45 PM)

How do you resolve the conflics if you cannot turn off the autopopulating folder when resolving conflicts? Not only every referenced VI has two versions but also every referring VI has two versions.

You can turn off autopopulating folders to resolve conflicts. That's possible today. What we're asking about is whether turning them off should be a side-effect of saying "use this VI" when the VI you choose is not in the autopopulating folder and conflicts with another VI that is in the autopopulating folder.