inspecting and editing <foundvi>

[stleric]

Hello,

Like the subject says, is there a way to inspect and edit the contents of the path shortcut <foundvi>?

The big picture: I have a project where I'm using two sets of identically named dlls and I want a relatively convenient way to switch between the two (consider them "development" and "production" sets).  Playing games with the "VI Search Path" option looks like a promising way to do what I want.  It also looks like if I remove <foundvi>, restart LabVIEW, and then restore <foundvi>, the restored <foundvi> comes back in a blank state.  It might be nice to have more fine-grained control over its contents.

If anyone has a more elegant way of switching between groups of vis/dll/whatevers en bloc I'd certainly like to hear it.

Or am I doing something fundamentally dumb?

TIA,

eric

[RavensFan]

What do you mean by "<foundvi>"?  What is a "path shortcut"?

[stleric]

---

@OriolesFan wrote:

What do you mean by "<foundvi>"?  What is a "path shortcut"?

---

So, (this is in LV2012, btw) if you go to the "Tools" menu, select "Options...", select the "Paths" category and choose "VI Search Path" over on the right side you get a list of things.  The things that begin and end with angle brackets are shortcuts (at least that's what I'm calling them, NI probably has their own nomenclature).  The thing/shortcut that says "<foundvi>" is suposed to contain a list of directories that the user has told LabVIEW to search for VIs that LabVIEW couldn't otherwise find.  This assumes the "Use Default" box is checked, if it isn't, "<foundvi>" may or may not be there.

eric

[RavensFan]

Thank you.  I've never had the need to mess with any of the paths in the option dialog which is why I'd never seen or heard of it before, so I've got no experience with trying to use that.

My gut feel is that trying to use that as away to deal with switching around dll's is all wrong.  Where are you using these .dll's?  Is it by using CFLN's?

If so, I believe you could put those into a case structure and have the different options call explicitly which dll you want to use.

Another choice, (maybe better, maybe necessary) would be to use the Conditional Disable Structure and have the different CFLN's in different cases.  Then you define symbols in your project.  How you set the symbol before running your code will determine which case of the structure gets called, and the disabled cases don't even get compiled, which could help prevent confusion within LabVIEW itself as to which of identically named dll calls are used.

I don't call dll's very often, so I could be mistaken and others with more dll experience can comment.

[stleric]

Yeah, me neither.  The few projects I've done so far all look like a bunch of loose VIs thrown in a folder, which gives you an idea of my level of sophistication.

As for tinkering with the calling VIs, that's  a no-go.  I didn't write the VIs that call the dlls and the state of those VIs is kind of fluid still.

Thanks anyway.

eric