What "bugs" me about this is there is a definition change required to adabpt to the new behaviour.
Opening the top level VI was all I used to have to do to to check the functionality of and file file specs of all of the VI's in my application. That used to inclue VI's in commented out cases.
It took me a while to stumble across this behaviour because I generally do not comment out code (there are exceptions) but will delete VI's that are not being used.
In this case I wanted to test the caller (the VI with the case) before I started development on the sub-VI.
I opened the VI in the morning and went to hierarchy screen (this is almost always the first thing I do after I open the top-level) to find the VI I wanted to work on.
THe issues re: the diagram disable
Again this is a feature that I have not used, but, I now understand something that I saw last week when we tried to open an app that had diagram disabled DSC code. We also saw the message that LV was looking for VI's we did not have on that machine, but opened anyway!
THe sub-VI showing up after opening the VI's FP makes sense because opening the FP loads the diagram (if present) and the sub-VI is on the diagram.
Re:suggestions of how to move forward.
1) I will never use a constant to comment out code ever again (I hope!)
2) VIT's already get special treatment in the hierachy with the "T" added to the icon. Greyed-out icons would be a nice way of specifying a VI is present but not called.
Enough for now,
Ben
