Run Block Diagram Cleanup on any diagram elements that are modified when "Save for Previous Version" is applied

[KarstenT]

The specific issue I've run into is that some newer LV features (like Auto-concatenating loop output tunnels and the expandable Merge Errors node) can be represented in earlier versions of LabVIEW with a more complicated combination of nodes and wires.  When "Save for Previous Version" is used, the equivalent code needs more diagram space, but ends up all crowded together on the block diagram.

Here's a specific example (sorry I don't have the original LV2012 source):

In this case, the empty array constant is actually connected to the shift register input of the loop that it is placed on top of.  This is completely invisible, though, and very difficult to decipher.  In my case, I tried to move that seemingly disconnected constant out of the way and inadvertantly broke the VI beahvior, because the wire was disconnected.

I've encountered this issue in particular when receiving support from NI Application Engineers using LV2012 who build sample VIs for me to test and then need to down-save them for me in LV2011. 

I propose that the "Save for Previous Version" automatically clean up the diagram for any nodes that needed to be changed/added in the down-save process (specifically to avoid overlapping and confusing nodes).

[AristosQueue (NI)]

Manzolli: And that would work if and only if we re-released the code for all the previous versions of LabVIEW. Save for previous can only do what the previous versions of LV could do at load time... all the work has to be done in the current version of LabVIEW because the whole point is that the previous versions have no idea what to do. This isn't about what's under the hood -- this is about what we shipped in plain view. 🙂 If you couldn't make it load, neither can we!

[Manzolli]

Sure!

[Darren]

Any idea that has received less than 3 kudos within 3 years after posting will be automatically declined.