And this is interesting for me, that I want to know why NI doesn't support this kind of handles ?
and we know before labVIEW opens a vi file. labVIEW will detect the target vi's version about. and do a comparing, if the vi file's revision is higher than the labVIEW system.
labVIEW will prompt a dialog box to tell user " labVIEW revisioin XX cann't open ......"
As this condition, why labVIEW cann't detect the block diagram (software component) automatically. and find whether the vi file which is higher one's component contained by the lower labVIEW system ? certainly, we can accept, lower revision labVIEW cann't open the higher one which is at the higher labVIEW's vi, because lower labVIEW hasn't it. or open it. as the lower labVIEW hasn't latest vis, and show empty. it is similar with labVIEW opens a vi which contains many subVIs that cann't be found.
sometimes, though the vi file was programed by the highter labVIEW system. but its vis are contained by the lower labVIEW's system too. this chance that I met many years, there are about 70~80 percent.
if NI can solve this trap, I think that will help user or a new user more available. and I think this technology is not hard for NI.
________________________________________________________
Try to make everything Automatic
