Hello all, I tried to search but couldn't find this topic. But I doubt if this has not been discussed already, in the LabVIEW forum. In my application, I have used customized controls. The application has several "parts" and each of them use "similar" (but not necessary the same) TypeDef controls that I have customized to suite the part. LabVIEW's good feature is that even if the control file is moved to another path, it finds and loads it, with a warning. However in my case, I need to turn this feature off, for some control file(s). Is that possible? I am using control files with same name, but they are expected for different "calling" VIs. If this is not considered a good practice, I may change names of each control file, adding a prefix/suffix of the calling application's name. Thus each control file becomes unique. But still this will remain a question. Because of small and appropriate names, I often prefer them with a "typical" name that I would give for such a control. Like in each application we have a "Main" program. And what I faced, the problem, is when I loaded a VI, it automatically "used" a control (with the same name like of the one that this VI expects) that is already loaded (from a different path) by an already open another VI, although the expected control exists in its expected location. It showed a warning, but didn't ask "do you want to load the original or use the one from the memory?" My question is, is it possible to have an "expected" path to be fixed, and not allow the VI to load the "recently" opened "same name" control as its expected control?The feature is good, but in some cases, can we turn it off or not?

Vaibhav wrote: Thanks for the comment Mark! Yes, that's true. But what about stopping the undesired connections from messsing up the program in the first place? I mean, before building a project. By the way, if we open a program through Project Explorer, it would still not allow to open a file whose twin brother is already in the memory. But will it shout before assuming a new connection on its own? No, the projects will work like libraries. Once you have the VIs as part of a project its name gets modified internally, or at least how to locate it on disk, which allows you to open both projects at the same time. The trick here is to do your work through the projects rather than opening the VIs directly. As long as you work through the projects themselves you can use two different VIs or typedefs with the same name located in different directories at the same time. That is as long as each one is the member of a different project.

LabVIEW

Load TypeDef/Control from a Fixed Path

Solved!

Author

I thought the same too.

Vaibhav

Message 11 of 11

(419 Views)

LabVIEW

Load TypeDef/Control from a Fixed Path

Re: Load TypeDef/Control from a Fixed Path