LabVIEW version of attached code

[Gregory]

Unless we are running the most recent version of LabVIEW, there are always going to be attachments uploaded that we can't open. It would be nice to know what LabVIEW version attachments were made in before downloading them and getting an error. It would also be good for the community to upload code in a lower version so that more people can use it. We can simply ask for it uploaded in a lower version, but is an annoyance on both sides to have to do so. With new posters, it can often take 4-6 messages to get code that I can actually open:

Please post your code.

     Here it is.

Can you upload for this version?

     How do I do that?

This is how.

     Here it is again.

About 13 years ago there was a great suggestion to put LabVIEW versions next to uploaded code, but I don't know how feasible it is. It has also been discussed here and here. The Tips for posting code document makes mention of uploading for a lower version, but I don't know how much visibility that gets.

Since it is already being enforced to attach the label of "LabVIEW" or "LabVIEW NXG" maybe a dropdown could appear to ask the user what version they are using. This drop down could be left blank, since many posts don't attach code or reference a specific LabVIEW version, but I think people would probably use it since they are already applying the product label.

What do people think, would this be a nice feature? Is this even an issue for other people?

[Hooovahh]

I don't know how much control NI has over the boards, but the version that a VI is saved is can be accessed pretty easily without needing LabVIEW.  I uploaded some code on how to parse the VI file structure over on LAVA.  Basically you find the "vers" block in the VI (search for the string vers) which gives you an offset in the file.  Go to that offset and you'll find the version of the VI.  Theoretically this could be written in any language (like php) and the web forum could add a line of text after the VI that says what version it is.  Of course things get complicated with other file types, and files might be in a zip, but still it would be helpful.

Also over on LAVA we have you select your preferred version of LabVIEW in your profile, so other people on the forums can choose to upload in that version, knowing you should be able to open it.

[LiliMcDonald]

Hi Gregory,

Thanks for all of the feedback. These enhancements are already in our backlog. We hope to implement these features when priority allows.

Thanks,

Lili

[Gregory]

Hi Lili, is this still on the horizon for a future forum update?

[Kristi_Martinez]

Hi Gregory,

Thank you for following up. While we do not yet have an estimated date for this request, we can assure you that our team is still tracking this adding software version to posts. I'm checking with our team to see if we can bump this request up in priority.

[Gregory]

Great, thank you!

[Kristi_Martinez]

Hi Gregory,
Unfortunately, our team is currently working on higher priority items and will not be able to address this as quickly as I hoped. However, this is still on the horizon.

[Gregory]

Alrighty, thanks!

[Kevin_Price]

Just to add my two cents after reading this thread and the linked ones.

I *very much* prefer that the LV version could be automatically identified for the attachment itself.  I'd have two problems with relying on something tied to my user ID:

1. It wouldn't be very meaningful as I don't have the same LV version(s) installed on all the PC's I support.  Things vary day to day.
2. When responding to a posting from someone whose code is from an even earlier version, I save back to that same older version (usually -- when I remember), even if I don't have that version installed anywhere.

I'm regularly a little frustrated when I scan a thread, prepare to answer a code question, download the code, create a new project so I can open the code without disturbing the project I'm really working on, and only *then* find out that the poster is using a later version than I have installed at my present location.  It'd sure be nice to see the version ahead of time so I could avoid all that trial & error time wasting.

I've only just begun to try to start a habit of indicating the LV version in the filenames of code that I post.  (I haven't done well so far, hopefully I'll get this turned into more of an automatic habit.)

-Kevin P

[Hooovahh]

Yeah I mentioned that on LAVA we have user specify a version in their profile, and as you stated it isn't perfect.  I'm usually working in multiple versions as you mentioned.  Still it helps to see someone specify a version and I'll remember to backsave to that version.  Occasionally someone's profile will say LabVIEW 2017 and they post code in 2020 and I'll mention that they should update their profile if they do prefer that version.

Also as for the helping people on forums goes.  Years ago I made a LabVIEW Tray Launcher.  It is able to take over the .VI file extension, and instead of running LabVIEW it runs my program when you open a VI.  It will then show you the versions of LabVIEW you have installed that can open the VI you are trying to open.  There are a few settings like if there is only one version of LabVIEW on your system that can open it, just open it in that.  And options for showing you what versions of LabVIEW are already running.  It isn't perfect and hasn't been updated in a while but should still work.  It makes opening random code from the internet easier if I just want to view the thing quickly.