How far back would you expect the version checker to go? LabVIEW 8.0? 7.1? I imagine if this functionality it would be almost like a big lookup table for features and if you saved for previous then it would consult these options.
I would suggest to have it check for the earliest version the current LV version can downconvert to. So it would be 8.0 right now for LV 2010/2011. If somewhere in the future, downconversion is changed to serve earlier or later versions, i think it would be valid to adopt (so if e.g. LV 2015 can downconvert only to LV 2010, the checker tool does not need to "track" back to LV 8.0).
Norbert ---------------------------------------------------------------------------------------------------- CEO: What exactly is stopping us from doing this? Expert: Geometry Marketing Manager: Just ignore it.
LabVIEW already does this according to the Help File. I also Tested this with the Start Asynchronous Call introduced in LabVIEW 2011 and the save for previous does show a warning that the function does not exist in previous versions. I would consider the error to Boolean an incomplete feature because its neither warned to the user or changed by the save for previous.
It seems to me this is a direct suggestion for a specific problem that a) has been marked as a bug (CAR 307993) and b) isn't a widespread problem, so unless I hear otherwise, I'm going to request this idea be declined as a bug.
If it is part of the LabVIEW requirements that code is successfully backsaved and a warning issued if not possible then feel free to mark this as "already in LabVIEW" The idea was not for the specifics of the bug referenced.
Define "successfully backsaved." If a VI calls a subVI that didn't exist in the previous version then the save for previous is successful but the caller VI is still broken.
I would at a minimum define successfully backsaved as no broken wires and no broken run arrow. By subVI I assume you mean things in vi.lib that do not exist in the previous version. I am not sure how you would handle that but if it is not possible then backsaving should give a warning.
I am still not clear if backsaving is always supposed to work or give warnings about incompatabilities or if it is just a shot in the dark. Should this be declined as "already in LabVIEW"?
