compare VIs with same name under LabVIEW 8?

[GabrielaK]

Hi,

if I remember correctly, LabVIEW 8 can now load VIs with the same name into memory, which means that a comparison between two VIs having the same name should work. Nevertheless, I get the same message like in older LabVIEW versions when trying to load those two VIs. Is there a fast and simply way for such a comparison without renaming one of the VIs?

Regards,

Gabs

[Ingo_Schumacher]

Hello Gabs,

thats true, LabVIEW 8 can handle VIs with the same name. But you have to remind that these VIs have to be placed in different VI libraries. Because LabVIEW works with both library and VI name to reference a VI in memory, it can still distinguish those two instances.

Thus, if you would like to compare two VIs with the same name you will have to create two libraries and add the vis one to each of them. This is working well - but if its just one vi you are talking of it might still be more convenient to rename it.

regards

[GabrielaK]

Hello Ingo,

thanks for your reply. Unfortunately, LabVIEW 8 still asks "view the VI in memory or replace it with the one from disk" when I try to load two VIs with the same name which are located in two different llbs with different names. I cannot rename the VIs itself, this would be too much work for all the VIs in the libraries which I have to compare. Renaming the llbs is no problem but doesn't seem to help. Do you have any other suggestion?

Best regards,

Gabs

[gmart]

I believe Ingo was speaking about the new project libraries in LabVIEW 8.0 not LLBs. While adding the VIs to project libraries will work, another approach would be to create an empty LabVIEW project and add one of the VIs to that LabVIEW project. The Compare VIs dialog will let you choose a VI in a LabVIEW project and the one outside the project that have the same name. You should then be able to compare the VIs.

[Ingo_Schumacher]

Of course gmart is right, I was talking of the project libraries. I know I should not have called them Vi libraries

Here is soem information as it can be found inside the LabVIEW help:

LabVIEW Project Libraries

LabVIEW project libraries are collections of VIs, type definitions, shared variables, palette menu files, and other files, including other project libraries. When you create and save a new project library, LabVIEW creates a project library file (.lvlib), which includes the properties of the project library and references to the files that the project library owns.

Project libraries are useful if you want to organize files into a single hierarchy of items, avoid potential VI name duplication, limit public access to certain files, limit editing permission for a collection of files, and set a default palette menu for a group of VIs.

You can view the structure of a project library from the Project Explorer window or in a stand-alone project library window. If the Project Explorer window is not open, navigate to a project library file to open it in the project library window.

You also can create project libraries from folders in a project.

Use project libraries to organize a virtual, logical hierarchy of items. A project library file does not contain the actual files it owns, unlike an LLB, which is a physical file that contains VIs. Files that a project library owns still appear individually on disk in the directories where you saved them. A project library might have a different organizational structure than its files on disk.

Use project libraries to qualify the names of VIs and other LabVIEW files. LabVIEW identifies VIs by filename. If you load a VI with the same name as a VI already in memory, LabVIEW uses the VI already in memory, an issue known as cross-linking. When a VI is part of a project library, LabVIEW qualifies the VI name with the project library name to avoid cross-linking. A qualified filename includes the filename and the owning project library filename.

regards

[GabrielaK]

Hi,

I guess I should have realized that... Thanks, creating two projects containing the different libraries was the solution. Thanks for your help!!! :womanhappy:

Gabs