I had a couple of points to add about file paths and linking. John Howard suggested a tree view with info about the file location. The VI Hierarchy window can show this info. If you select the "Full VI Path in Label" option (it's in under the View menu). Moving the mouse, you can scan through your whole app fairly quickly. With some practice, VIs which are not in your expected tree will be easy to spot.
The other gotcha is the clipboard. If you copy a VI (ctrl-C), and then close all VIs, the copied VIs and all its subvis will still remain in memory. If you open another project and any VI names are shared, they will link to the old copied VIs. If you keep the hierarchy window open and test it out, then you can see how this happens, but it's easy to overlook if you are not thinking about it. If you Ctrl-C copy some non-VI object, like a piece of text or an indicator, before switching projects, you will never have the problem, but it's easy to forget that. My best advice is to fiddle with the copy command, and the hierarchy window and understand the behavior, then always be on the lookout for warnings from LabVIEW about locations changing or files needing to be changed before you have made any edits. Jason Dunham SF Industrial Software, Inc. -----Original Message----- From: Howard, John [mailto:[EMAIL PROTECTED] Sent: Monday, March 01, 2004 8:59 AM To: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: Confounded and Ranting I wonder if the following would be useful. How about a tool using a tree view control, which would present a hierarchical overview of a LabVIEW application in the left pane of a window, and detailed VI/Library information in the right pane. One of the details presented could be where the VI is loaded from.
