NI Home > Community > NI Discussion Forums

LabVIEW Idea Exchange

Showing results for 
Search instead for 
Do you mean 
We've turned on a search before post feature in the LabVIEW Idea Exchange. This new feature will help cut down on the number of duplicate ideas in this space!

The NI Idea Exchange is a product feedback forum where NI R&D and users work together to submit ideas, collaborate on their development, and vote for the ones they like best. View all of the NI Idea Exchanges to post an idea or add your opinion on an existing one today!
New Idea

Right now - Requried Terminal is identified by either 1. Bold text in Help window 2.Broken arrow.


Will it be posible to highlight / mark the required terminal, so to identify at first look ? Something like mentioned below.


VI.PNG           zoom.png zoom3.png


Sorry i couldnt draw properly. but some thing like this to highlight both in FP and BD.


Close Project

Status: New
by Trusted Enthusiast on ‎03-21-2015 02:03 PM



  It would be very usefull to know which VIs are still running.


To Ensure readability of  the code - Remove bundle and Unbundle from function palette ??






Lock text in center

Status: New
by Trusted Enthusiast on ‎04-13-2015 01:13 PM


                                                           "  lock text in center  "





                                        ... sorry ..  but the text is not in center


                  A > B , and the difference is greater than one pixel




Wire : Right Click --> Visbile --> Label  (Its void Now )


1.png                                  2.png


Solution : It can take the control Name as default label of the wire,  instead of  being Void





Not sure if this idea is already proposed. 



Index & Bundle Cluster array should retain element names

Status: New
by Knight of NI ‎02-13-2015 11:31 AM - edited ‎02-13-2015 11:32 AM

(Inspired by this discussion)


The Index & Bundle Cluster Array function currently discards any labels of the input data. I think it would be more useful if it would try to retain the names (i.e. copy the original array labels (if available) to the element labels of the output).


The picture illustrates the idea. On the left we see the current behavior and on the right what we would get after this idea is implemented.


Event Timeout Terminal (Event Structure)

Status: New
by Trusted Enthusiast on ‎03-14-2015 06:23 AM


                  A picture's worth a thousand words












Include longstanding "known issues" in the help file

Status: New
by Active Participant X. on ‎03-09-2015 01:17 PM

NI updater kindly informed me that LabVIEW 2014 SP1 was released (even though I uninstalled it shortly after I tried it last year) and out of curiosity, I took a look at the known issues list.

I learned a few interesting things I did not know about, and also that some problems had been reported as long ago as version 7.1.1. This type of stuff looks like bugs that won't be fixed, ever.

For instance, CAR #48016 states that there is a type casting bug in the Formula Node. It was reported in version 8 and the suggested workaround it to use a MathScript Node instead of a Formula Node (where is the "Replace Formula Node by a MathScript Node" contextual menu item?).

Problem: the MathScript RT Module is required. Even in my Professional Development System, this is not included by default. Does this really count as a workaround?

I read: we don't have the resources to fix that bug, or we don't want to break code that expected that bug.

In any case, this bug with most likely never be fixed.

The bottom line is, we can waste a lot of time as users, rediscovering bugs that have been known for a while and will probably never be fixed. As a user, I would really appreciate a courteous warning from NI that there are known traps and have a complete description handily available with the help file related to the affected function.


My suggestion: add a list of known issues (with link to their description) for all objects, properties, functions. VIs, etc, in the corresponding entry in the Help File.

Add an option to remove items in memory

Status: New
by Active Participant dsavir on ‎03-30-2015 02:41 AM

After deleting items I don't want in the project, or loading plugins in a  plugin architecture, I want to remove them from the LabVIEW memory. This is not possible now, as they go into Dependencies->Items in Memory.

Items in memory.PNG

The only way to do this now is to close and open the project, which over a large Plug-in architecture project is a real pain. 

Ideally, I would like to right click the folder and choose "remove from memory". However, any option that allows this would be good.


Thank you!



Add Control Anchors to Labview

Status: New
by Member ngarneski on ‎02-11-2015 02:44 PM

.net and many other languages have an intuitive and simple way to allow you to define how a window behaves when you resize it: anchors.  Anchors allow you to define the distance between an edge of a child control and the edge of a parent control regardless of the size of the window. The size of the control itself stays constent unless it violates the rules of the defined anchors in which case it changes sizes to meet those rules. For example a front panel with the following anchors:



Would be resized into:



remove thick wire corners under Select block

Status: New
by Member Enrico_Segre on ‎03-10-2015 05:19 AM

Aesthetic issue: thick wires connected to Select inputs show as ugly corners behind the triangle icon, probably a result of the underlying connector pattern.This does not happen for other triangular blocks, at least not up to a reasonable wire thickness (to make a wire thicker, just make a N-dim array of something).


Snippet Palette in Block Diagram

Status: New
by Member sandyy on ‎03-24-2015 10:58 AM

Populate all snippet captured in function palatte for reusability



Replace Enum with Tab and Vice Versa

Status: New
by Trusted Enthusiast on ‎04-09-2015 04:48 AM

It would be really nice to have a feature to Replace an Enum with a Tab and the Tab control contains the items which was configured in the Enum control. This would work the either way by replacing a Tab with an Enum containing the Items configured as Tabs. This makes sense because both are of the same data type.








Problem: my code accesses many different properties of many different controls. I need to locate where a specific property of a particular control is read/changed.




I know that the Find panel offersi me the option of searching by text, like


Screenshot from 2015-02-01 13:46:10.png

but that is not the solution, because I need to type thename of the property, and because I may match many other objects with the same string (comments, other controls with the same property, etc.)

I'd like a faster way to get to where I need. For instance the contetual menu could offer Find/specific property according to where the right-click was.

How you ever had to design a SQL query? Probably :smileyhappy:

Usually I design these in MS SQL Server Management Studio, because its easy to test there. And I like that the sql code is colored, so its easy to see whats going on.

However, when I copy it into a string constant, the colors are gone:



But I noticed, that if I copy sql code into a mail or a document, the formatting from MS SQL Server Management Studio is preserved.

That is because the program stores RTF (rich text format) information on the clipboard.


Wouldnt It be nice if there was an 'Paste Special' or Quick Drop feature that preserved the RTF formatting when pasting text into a string constant or a documentation label?


Then it could look like this:



If you think that this could be a nice feature, then kudo this idea :smileyhappy:

Comparison Palette Better order

Status: New
by Active Participant Manzolli on ‎02-10-2015 06:17 AM - last edited on ‎02-10-2015 09:39 AM by Trusted Enthusiast

Very simple idea that can make locating the basic comparison functions more efficient (first two lines). Changing the order putting each comparison function and his counterpart below him would make easier to find the desired one.


Now: Comparison palette.png        Proposed: Comparison palette - rearranged.png

Environment Variables in paths

Status: New
by Member TaKend on ‎03-26-2015 02:01 PM - last edited on ‎03-30-2015 10:31 AM by Trusted Enthusiast


This should work!! I know there are workarounds and I have used them but it would be much easier.  



On Windows, you can define environment variables that auto expand to known directories. There are some variables that are already defined by the system. For example, %TEMP% automatically expands to c:\Users\<username>\AppData\Local\Temp OR WHEREVER THE USER MOVED TEMP DURING INSTALLATION. That's the important part .That makes it possible to write %TEMP%\abc as a symbolic path that works regardless of how the system gets reconfigured.


Users can define their own environment variables, and those get expanded when used in a path in the command line or Windows Explorer (the text entry region at the top of an Explorer window). On Linux and Mac, it is the equivalent of using $VARIABLENAME/abc, where VARIABLENAME is some user-chosen name.


[admin edit] Added background information on environment variables, and updated title to use the word "Environment" instead of "Environmental".

Flow control for Exit and Quit

Status: New
by Member sandyy on ‎03-30-2015 01:20 PM

Flow control for Exit and Quit. 




Similar ldea as flow control to delay proposed.





Currently, if the user edits the X or Y position of a cursor, this doesn't fire any event (that I am aware of), while in effect is is equivalent to the user grabbing the cursor and instantaneously moving it to a new location.

There is a "Cursor Move", "Cursor Release" and a "Cursor Grab" event, as well as possibility to catch the user selection of a cursor contextual menu event such as "Bring to Center".

It is possible to check whether the user 


My suggestion: Add a "Cursor Location Edited" event for Graphs with cursors


Latest LabVIEW Idea Exchange Blog Posts
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
User Kudos Count
Idea Statuses