LabVIEW Idea Exchange

Just 5 min ago I was in the situation that I downloaded an example VI from an NI support forum. I double clicked it and I got the message that the LabView-Version that was used for storing the VI is newer that my LabView version 😞

Most likely the VI could run without problems on my old Version (LV2009).

What I suggest to get around this kind of problems are two things:

1) create a web-based service (maybe only for registered users) where users can upload single VIs or ZIP-Files with a complete program structure. The VIs should be converted to the selected LabView version and send back to the user together with a conversion report.

2) integrate this service into LabView: If the user tries to open a VI that was stored in a newer LV version, LV should connect (after user confirmation) to the NI-Server for automated VI conversion.

One example is shown below from the Device Driver Installation dialog but there a many similar cases. It is very difficult to obtain a decent overview having such a small window for the tree display.

I suggest as a general style guide to always enable the resize option in a dialog box whenever the layout requires a scroll box.

I have a hard time to see what could be reasons not to do so.

It would be helpful to have a way to code sign your software for Mac OS X Mountain Lion to get suppport with the new GateKeeper fiunctionality.  Having a code signing option in the application builder would be perfect.  More information:  https://developer.apple.com/library/mac/#documentation/ToolsLanguages/Conceptual/OSXWorkflowGuide/DistributingApplicationsOutside/DistributingApplicationsOutside.html#//apple_ref/doc/uid/TP40011201-CH12-SW2

I've had a look around and can't see anything in here like this already (which surprises me so I'm suspicious that it's just the search algorithm failing) but I'd like to see options in the LabVIEW Project tree for changing target hardware.

For example, I have a development underway using a cRIO-9114 chassis with a 9024 controller, and a 9144 EtherCAT expansion chassis. The primary chassis is about to be upgraded to a 9116, as we need a bigger FPGA, and although the hardware upgrade process is straightforward, upgrading the chassis in the LabVIEW Project is not a possibility. Instread, I need to create a whole new target, and copy and paste every VI, node, FIFO, DMA etc. across. There's quite the possibility that I'll miss something, or the new target won't have all the same settings (Scan Mode period and priority settings for example), leaving me with that niggling feeling that something under the hood will be wrong. It would be much neater if this was an automated migration.

Furthermore, as the hardware is not here yet, I need to create the new target and all it's modules manually, which will take me quite some time. An automated migration would save me that trouble.