From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
Hi all, For a lot of reasons, I have to work with several LabVIEW versions.
My biggest fear is to save something in a later version : projects are quite big, and a save for previous version is hard when using terce parts (such as OpenG, JKI, etc.)
My whish would be to have a warning message when I save a vi in a new version, such as :
"You are saving a 8.2 file in 11.0 : do you want to continue ?"
Good idea. A nice addition might be a global option to protect VIs from being saved a newer version... Locking/unlocking is a pretty tedious workaround when working with multiple projects in multiple LV versions.
Your idea to add a "Locked/Unlocked" option to a vi//project is a verry good idea !
Well- you should be using some form of source control. But, at the very least protect you code by setting the windows read only property and select Treat read only vi's as locked in the enviornment page from Tools>>Options.
I would suggest the warning for newer version of LV should be seen when the VI is OPENED (inclucing option: Open all VIs without prompting again).
The reason for this is to avoid making a lot of changes to a VI and THEN discover that it was opened in the wrong version.
I used to have a homemade tool for this (replaced LabVIEW.exe in registry) but since LV2013 the registry is continuously kept updated by LabVIEW overwriting my changes (just like a virus :-).