Caveats for Using the LabVIEW Example User Interfaces

Consider the following issues when using the example LabVIEW user interfaces:

• The Load Top-Level VI.vi, located in the <TestStand Public>\UserInterfaces\Full-Featured\LabVIEW\Source Code directory, launches the LabVIEW user interface in the context of a LabVIEW project.
• If you use the files located in the <TestStand Public>\UserInterfaces\Full-Featured\LabVIEW\Source Code or <TestStand Public>\UserInterfaces\Simple\LabVIEW\Source Code directories as a starting point for creating a user interface, NI recommends that you always run the user interface in the context of its LabVIEW project to avoid name collisions. If you expect the user interface to run outside the context of the LabVIEW project, you must modify the names of the VIs in the user interface to ensure the names will not collide with the names of code module VIs or its subVIs.
• A LabVIEW project library provides a namespace for the LabVIEW simple and full-featured user interface examples. If you load any VI from the user interface by name, you must update the code that loads the VI to include the namespace.
• When you run the TestExec.exe build specification to generate an executable, LabVIEW prefixes VIs listed under the Dependencies node in the LabVIEW project with Simple UI - or Full UI - for the simple and full-featured user interfaces, respectively, to avoid name collisions. If you load any VI from the user interface by name, you must update the code that loads the VI to include VI prefixes. Complete one of the following options for all dynamic calls listed under the Dependencies node, including VIs that you call from top-level files but that you have not explicitly added to the My Computer target in the LabVIEW project, to resolve this issue:
  • Add the Simple UI - or Full UI - prefix to the path you pass to the Open VI Reference function when the caller VI runs in the LabVIEW RTE. You can use the Application:Kind property in LabVIEW to determine whether the VI is running in the development system or the LabVIEW RTE.
  • Add the VIs listed under the Dependencies node to the My Computer target to prevent the name change when you build the executable. LabVIEW prefixes only the files listed under the Dependencies node. NI recommends that you prefix these VIs manually to avoid potential name collisions that might prevent the user interface from running VIs that have conflicting names.