Save for oldest version possible

[3esmit]

There is one particular reason for saving in LabVIEW 2015? I understand that sometimes some features are unavaliable on older versions. I'm currently downloading an avaliation version of LV2015 to test this code, maybe I pull request this project in older version.

[francois-normandin]

I believe I used some of the latest Utility Variant VIs in 2015. If you want to backsave the project, it is likely that some of the VIs will need to be modified to use either OpenG Variant tools or some of the deprecated Utility Variant functions from vi.lib.

Thanks for your interest in this webinar! Let me know if I can be of any help.

[3esmit]

This VIs are sadly password protected so I could not check if they had the same output but seems like so, as the terminals are the same and the VI names are get type.

I created the pull request, everything seems to work in my 2013 version. I believe this Webinar is very important for LabVIEW ecosystem and should be ported to the older version possible.

[francois-normandin]

Thanks Ricardo. I'll checkout your backsaved code when I get a minute! State Machine Objects have been created with 2013, so this is as far back as we will maintain the base class code. I'll take note to prepare any future webinars in LV2013. ;-)

Indeed, the Utility Variant VIs are password-protected. They are likely wrapping a direct call to LabVIEW.exe.

[3esmit]

Its just missing the fix in Camera.TestLauncher that is a Error Clean.vi not replaced for 2013 version. Also I don't find those JKI user interface libraries

[francois-normandin]

JKI User Interface libraries should have been removed. It is an invalid cross-linking somewhere. Possibly in a disabled diagram. They should not be called anymore.

[3esmit]

They are used in Camera.TestLauncher. I will remove them from repository then.

[3esmit]

Done.

[francois-normandin]

Merged.