I have a teststand framework that contains two folders that serve as VI "libraries", with several hundred Vis each.
Up until this point, I have not collected the Vis into project or vilib files.
In order to be able to run multiple versions of our code on the same machine and not worry about "cross contamination", I collected the Vis into a vilib and then a project file. I updated all teststand calls to point to the projects.
This has caused the sequence editor to slow to a crawl during editing. For example, inserting a statement step takes 5-10 seconds, navigation has constant latency, and editing statements is delayed and extremely frustrating.
I have found that disabling the search directory containing the VI allows the editor to be responsive.
1) I need to keep the Vis in project files, in order to separate the name spaces, correct? Operators open more than one version all the time on our testers.
2) is there a way to fix this and keep the search directory?
3) do I need to keep the project files, but move to relative paths and not search paths? If so, is there an easy way to convert the found VI locations to relative paths? Or will I have to adjust each instance?