LabVIEW Idea Exchange

Checkout

NASA JSC Concept M Video, http://www.youtube.com/watch?v=kFPNcWN7QnM

Robonaut in space, http://www.universetoday.com/2010/03/24/iss-to-get-man-cave-complete-with-robot-butler/

http://www.google.com/url?sa=t&source=web&ct=res&cd=1&ved=0CAsQFjAA&url=http%3A%2F%2Fciteseerx.ist.psu.edu%2Fviewdoc%2Fdownload%3Fdoi%3D10.1.1.107.349%26rep%3Drep1%26type%3Dpdf&ei=sUy_S-TOEsqmnQfuv5GGCg&usg=AFQjCNGlmmF_I-pjMmCn26S7Pj8biWFxRA

If GM can mass produce the R2 for DoD and in the future for commercial applications the potential is tremendous.

Pavan

Please implement a way to generate reports in ODF (native format of OpenOffice) as it is a file format everybody can read (.doc is not because you must buy Microsoft software).

If you do that, programmers will automatically be able to generate PDF because OpenOffice has a dos command to convert any ODF document to PDF.

I know we have some ways to personalize the Getting Started window but to my taste, it's not enough!

What exists right now could be integrated into a SubPanel to keep the same functionality and that would also let anyone make it's own little plugin into this windows.

Here's a little example :

It would be nice that if a VI documentation set is created into HTML with PNG as picture format a snippet option would be included.

This option would embed a VI snippet of the top-level BD inside the PNG instead of a static image.

This way it's possible to distribute the code inisde the documentation.

Currently it's only possible to have drag and drop events for files on a path control.

It would be usefull if we could have drag and drop events for files on any control.

This way simpler GUI can be build with a very nice user experience.

Ton

When creating an installer for a built LabVIEW application, it is very difficult (see here) to include an additional 3rd party installer (such as a device driver or application that your built application depends upon).  What I'd like to see is a solution that treats 3rd party installers as first class citizens.  I'm imagining a new "Additional 3rd Party Installers" page of the Installer build specification properties dialog.

This page might look something like the one in the screenshot below, allowing users to add a folder that contains the 3rd party installer files and define a command that is run inside that folder during the install process.

When LabVIEW builds the installer, it would suck the additional installer folders into the main installer and, after installing your app files and the additional NI installers, it would sequencially extract your additional 3rd party installers into a temp folder and then execute the command line to run.  This is a pretty simple scheme that would really simplify the process for end users.

I'm sure I didn't address every issue of this use case, so please, everyone, feel free to add your own ideas.  I'd love to hear your comments.

When you’re making a By Reference LabVIEW Object using a Data Value References (DVRs) the user of your class would need to embed each Dynamic Dispatching VI inside an In Place Element Structure (IPE). Or you have to create wrapper VI for each method but this undermines the advantages of LVOOP Inheritance.
 
The idea is that a DVR containing a LabVIEW Object wired to a Dynamic Dispatching Terminal is equal to calling the Method VI inside the IPE structure like illustrated below.