LabVIEW Idea Exchange

Community Browser
About LabVIEW Idea Exchange

Have a LabVIEW Idea?

  1. Browse by label or search in the LabVIEW Idea Exchange to see if your idea has previously been submitted. If your idea exists be sure to vote for the idea by giving it kudos to indicate your approval!
  2. If your idea has not been submitted click Post New Idea to submit a product idea to the LabVIEW Idea Exchange. Be sure to submit a separate post for each idea.
  3. Watch as the community gives your idea kudos and adds their input.
  4. As NI R&D considers the idea, they will change the idea status.
  5. Give kudos to other ideas that you would like to see in a future version of LabVIEW!
Top Kudoed Authors
Showing results for 
Search instead for 
Did you mean: 

Do you have an idea for LabVIEW NXG?

Use the in-product feedback feature to tell us what we’re doing well and what we can improve. NI R&D monitors feedback submissions and evaluates them for upcoming LabVIEW NXG releases. Tell us what you think!

Post an idea


 A picture is worth a thousand words.

This new button should finish the actual VI and close it instantly.

When using the LabVIEW Internet Toolkit FTP library to transfer large files, there is no way to determine the progress.


I propose a notifier be added to the FTP Registry object data. This notifier would be updated by the low level TCP Read Stream and TCP Write Stream vis and monitored by a UI to display progress of the transfer.


See this NI Forum post...


FTP transfer progress bar 





In LabVIEW 2009, the programmatic API for shared variables and I/O variables was introduced. This allows you to reference a variable by name, rather than dropping a static node on the diagram.


Some of the benefits are: iterating over many variables with looping structures, creating modular code, and dynamically accessing variables based on names in a config file for example. 


Programmatic access to single-process shared variables would also be useful.


(Single-process variables are effectively global variables (not network published), but use the same static node as the shared variable and are contained in project libraries.) 


The problem: Free Labels may take too much space on BD to hold all information.


Idea 1: Allow Label to have help. With this simple change, the programmer puts the essential information in the label and the details in the help.


Idea 2: Create an option to current Free Labels or create a new kind of Free Label, that has a behavior which a hidden part of the information is shown, in a drop-down "flap", when the user hover over the Free Label. The label could have two fields, one for the permanent information always shown (current bahaviour), the other for the additional information that will be shown when the user hover over the Free Label.


Free Label with Drop-down additional information.png



When installing a new version of LabVIEW, I always find myself resetting all of the options I previously changed from the default settings in the Tools -> Options menu. This means I have to spend my time remembering what options I changed and where in the Options menu I need to change them. It would be nice if a newer installation of LabVIEW looked at the older version's Options settings and then applied those settings to the new installation.


The same idea applies to how I configure the palettes on the block diagram. It would be nice if newer installations looked at how I configure my palettes and then set them up the same way. 


With these changes transitioning to a newer version of LabVIEW might be even more seamless for users that change their settings from the default settings. 

Many users already talked about adding new controls and revamp the current ones. In this topic I will address many issues that I have about the Meter control. Even though I like it a lot, it would be nice if it has more flexibility to customize. Here some ideas:


1) Color ramp issues:

    • Is asymmetric: there is a hidden color in the right most side, that can be only be seen when you change what you think is the last color (red). With the “Interpolate color” option off it is very hard to see and change it;

    • Has a limited fixed number of color steps to customize the ramp looks;

    • Cannot be customized in properties window;

    • Strange correlation between the modes on and off of the “Interpolate color” option:


Meter control colors.png


    • Enabling an option, the ramp could appear progressively follow the needle:


Meter control progressive ramp.png



2) When resizing, it would be nice to be possible to change the control's aspect ratio making all internal elements proportionally follow the change.



3) The user could have an option to rotate it in 90 degrees steps, allowing four positions: normal (0 degrees), right (90 degrees), upside down (180 degrees), left (270 degrees):


Meter control 90 degrees.png


(The numbers on the scale should be rotated and appropriate 3D shadows should be applied)


4) The needle course could have a parameter to determine the curvature. A positive number will give the current aspect, let's say convex. Zero will make the needle become a slider. The nice thing of this is that you can start with something looking as a Gauge (very convex), passing to a Meter (slightly convex), to end with a Slider (strait). I doubt that a concave look, with the needle pointing to the center will be useful because the idea is to make the reading as much clear as possible.


I'm Sorry I didn't made pictures to illustrate this case because I have no enough skills do it. I tried to be as clear as possible in the text. If anybody needs any additional information, please let me know.

 Since there is a lot of space we can have a save button which will save a click to save the vis. Another addition is to greyout the button when the save is done or an action is reverted back.



 With save button





With save button disabled.


I find the stacked chart useful for separately displaying individual channels of time-aligned data on a common X Time axis.  If the number of acquired channels is changed at run time, one would hope to correspondingly change the number of plots in the stacked chart.  It currently is not possible to change the number of plots on a stacked chart at run time.


An option might be to use a Mixed Signal Graph instead but it does not seem possible to easily add or subtract plot areas at run time and have them occupy equal percentages of the plot area like the stacked chart's plots do.  Additionally, the Mixed Signal Graph has the advantages of being able to use cursors and not having to know and define a chart history length.


I often make small For Loops using Auto-Indexing, and only occasionally do I use either the Iteration Terminal or Count Terminal. My current practice is to tuck the Iteration Terminal under the Count Terminal just to get it out of the way, shown below. I propose that these two terminals can be shown or hidden (circled in green), just like the Conditional Terminal.




Here's an example of the new lower-profile For Loop with the unnecessary terminals hidden:



 It is a very common / preferred practice to design Vis along a horizontal structure of error clusters wires.


Sometimes, cleanup does not create a horizontal error wire.


Please add a  "force error wire horizontal" option.




In existing "File Dialog" Express VI- configuration Dialog we can specify what we want to select(File/Folder), wheather its new or existing File etc.

However for specifying File Pattern, Pattern Lable, Dialog name etc. we must connect constants from outside. it takes lot of space.

it would be great if those options can be configured from pop up.

For example:

1) install based on a license: this would install only the software related to a license;

2) reinstall/update based on license OR based on what's already installed.


For every new update of LabView I need to select the installation  of the toolkits I want, why not make it faster?

I would like to propose the use of a stacked parallel execution structure.  Especially in FPGA applications, this will solve the problem of diagrams running off the screen.  All execution pages will run simultaneously as if independent while loops were scattered across the BD.  This idea potentially leads into a 3 dimensional visuallization of coding LabVIEW. Note: In the image, the pages are offset but should look similar to a stacked sequence structure.



Parallel Execution Structure 3.JPG



When you connect the error wire to a case structure selector, you get two cases for error and no error. I think you should be able to add in cases for specific error numbers so you can handle specific errors differently. You could do this currently, but you would have to unbundle the error and use the error code.


Numbered error case.png

We have a Round towards -Infinity  (3.8 becomes 3,  -3.8 becomes -4)

We have a Round towards +Infinity (3.2 becomes 4, -3.2 becomes 3)

We have a Round to Nearest (Rounds up or down to nearest integer, if 0.5, banker's rounding to even integer)


Why is there no Round towards Zero?  Basically a truncate.  (3.2 becomes 3, -3.2 becomes -3)

I have a use for that right now, but it takes several primitives to work. 


As a corollary, a Round Away from Zero.  (3.2 becomes 4, -3.2 becomes -4)



Message Edited by Ravens Fan on 01-19-2010 04:53 PM

Building on the "Path Case Selection" idea, it can be difficult to remember all of the values of an Enum when defining a case structure.  I suggest a popup menu on the case structure which lists available values for selection.  Values already defined in other cases could be greyed out, and values selected in the current case could be selectable for removing.  Perhaps it would require a heading to differentiate from selecting a case, and Ctrl-click (Ctrl-right-click?) to activate.

Case Popup

This idea simply extends "Allow References to be wired into Case Selectors" by JackDunaway.  In short, allow paths to be wired directly into a case selector, with one case for "Not a Path", one for "Empty Path", and a third for "Valid Path".  This would often save me small trees of nested cases.

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.

DVR DynamicDispatch.PNG

Message Edited by Support on 01-15-2010 04:39 PM

Since the commands "Group" and "Ungroup" objects it is only available in the FP's toolbar, there is no way to customize a shortcut key to it. The proposed ideas are:

  1. Have the controls also available in the "Edit" menu to allow us the customization through Tools -> Options... -> Menu Shortcuts.
  2. NI define two keyboard shortcuts, for example, Ctrl+G to group and Ctrl+Shift+G to ungroup.

Sometimes, like in many other software that have a paint feature, we need color swapping between foreground and background. The idea is to add a spot in the Tools Palette to allow this operation in one click. Here is a suggestion:


swap colors.png


It's difficult to see the spot because I did not changed anything, just added the double ended arrow. One way to help the visibility is turn it white when the mouse hover over it.