The solution would be, and I was under the impression that was what it did, to use VI server to launch the file in a specific LabVIEW version. The Datact version chooser in my opinion would have a chance to do the right thing although it is by far not trivial. There is really no way to version automatic file launching for the same file type, simply because you can not do a 1 to n selection automatically.
LABVIEW 8.0 REGISTRATION
NI probably never has looked much into that anymore since it is both unsupported technology as far as MS is concerned and the registration of different LabVIEW versions for the same files would be mostly a hack anyhow as it is only a UI feature of the Explorer where you get multiple sub menu items under the Open right click menu.
LABVIEW 8.0 WINDOWS
Microsoft itself does discourage to use DDE since about Windows NT4 for anything, although it is still the standard way of launching files into a running application.
Recent Windows versions added a possibility to register multiple applications for the same file type but this is in fact at best a hack IMO.
You could say that this is a bug but unfortunately since the whole file association in Windows is based on file endings only and therefore a file traditionally only has one association there was very little use in trying to be smart and use versioned DDE server names. LabVIEW uses the same DDE server name in all versions. On failure it launches the registered executable passing it the file path as argument instead. The registry defines for the file type a DDE server name and an application topic and the Windows shell (the part that basically sits above the actual Win32 API and where the File Explorer is the UI of) attempts to contact the registered application through DDE and if that succeeds it passes it the file path to open. The specific problem you see is that the actual launching of a file in an already launched application is done through DDE. The registry defines which program should be started for a specific file ending and obviously you can not really register more than one primary application for a single ending.
LABVIEW 8.0 MAC OS X
I think Mac OS X still supports that but they also went the path of basing most of the launching on file endings instead. The reason is the limited file association based on file endings instead of Meta data as was used in the old Mac OS Classic Desktop interface. There is no way to fix that really as far as Windows goes. So does anyone know of a way, to prevent LabVIEW from remembering what version was last ran? I've tried adding the "RegisterExtensions=False" key in the LabVIEW.ini files (it was suggested at NI's forum this may fix it) I've also probed the Windows registry and any any reference to "LabVIEW 8.0LabVIEW.exe" I replace (one at a time) with "LabVIEW 7.1LabVIEW.exe" and it did not help. A larger bug (which is related to this one) is if I run the command line "C:Program FilesNational InstrumentsLabVIEW 7.1LabVIEW.exe" "C:test.vi" it will open the test.vi in the 8.0 version of LabVIEW. If I run LabVIEW 7.1, then run LabVIEW 8.0, then minimize both, then go to the start menu and run LabVIEW 7.1 again, the LabVIEW 8.0 window will be brought up. Ok lets say I have LabVIEW 7.1, and LabVIEW 8.0 installed in a Windows machine. I've seen this problem and I don't think there is a solution So does anyone know of a way, to prevent LabVIEW from remembering what version was last ran? I've tried adding the "RegisterExtensions=False" key in the LabVIEW.ini files (it was suggested at NI's forum this may fix it) I've also probed the Windows registry and any any reference to "LabVIEW 8.0\LabVIEW.exe" I replace (one at a time) with "LabVIEW 7.1\LabVIEW.exe" and it did not help. But I know what version of LabVIEW I want to run, based on predefined shortcuts and installation paths. I think NI's mentality is that LabVIEW should remember the last version that was ran, for convience when opening new code. A larger bug (which is related to this one) is if I run the command line "C:\Program Files\National Instruments\LabVIEW 7.1\LabVIEW.exe" "C:\test.vi" it will open the test.vi in the 8.0 version of LabVIEW.
0 kommentar(er)
