Downconverting the VIs posted in Forums

[Neos]

I am not sure it is a valid ask ( and if it is then someone has suggested already )

Whenever we go to a post from a user asking for help or we post any suggestion VI which others want to see for reference number of times we get a popup saying current vis version is newer than your version.

Atleast for the VIs posted in forum can NI do someting like it will be open in our version regerdless of the version we have and the VI has been saved. Ofcourse the new function which are there in New version and not present in old versions will be shown as question mark.

We have version conversion board but i think its too much ask for VIs posted for asking help and giving help.

[crossrulz]

I don't like the idea of auto conversion.  What would be nice, though, is if the LabVIEW version was listed with the attachment, much like is done with the communities.

[altenbach]

---

@crossrulz wrote:

I don't like the idea of auto conversion.  What would be nice, though, is if the LabVIEW version was listed with the attachment, much like is done with the communities.

---

Ever since they started playing with the semi-broken deep inspection of attachments, you would think that the VI version information could be added automatically with a little more code. 😉

[crossrulz]

---

@altenbach wrote:

---

@crossrulz wrote:

I don't like the idea of auto conversion.  What would be nice, though, is if the LabVIEW version was listed with the attachment, much like is done with the communities.

---

Ever since they started playing with the semi-broken deep inspection of attachments, you would think that the VI version information could be added automatically with a little more code. 😉

---

At this point, I would just like to be able to post VIs.

EDIT: Just noticed Christian gave the same link...

[JÞB]

This is one of those reasons to encourage snippets!

• version info is visible
• vi diagram is visible (even mobile)
• searching is improved (oh- something like that!)
• comments in code explain points of interest
• Can be modified under the right phase of the moon.

More snippetts please (and float a link to the CCT for usesr that use events and linked p-nodes)

[altenbach]

---

@JÞB wrote:

This is one of those reasons to encourage snippets!

• version info is visible
• vi diagram is visible (even mobile)
• searching is improved (oh- something like that!)
• comments in code explain points of interest
• Can be modified under the right phase of the moon.

More snippetts please (and float a link to the CCT for usesr that use events and linked p-nodes)

---

Of course we should also menrtion the disadvantage of snippets:

• connections to the connector pane are lost.
• Front panel is not visible (typically)
• Code in other frames of case structures, event structures, stacked sequences, diagram disable structures, etc. is not visible unless snippet is loaded into LabVIEW
• ...

When I post a snippet, I typically also attach the actual VI.