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

Make it possible to scroll through the items within a picture ring using the mouse wheel.

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.


.NET charts

Status: New
by Active Participant ASTDan on ‎02-19-2015 10:44 AM

I stumbled across this today


It is an XControl created by Thoric that allows LabVIEW users to acess Microsoft .NET Charts


I think NI should put some development effort into this.  It would be a great way to get some new cool charts.



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:



3 Improvements of the Table controls

Status: New
by Member G_Mulder on ‎02-25-2015 08:08 AM

The Table is an important UI feature allowing cell widths adapted to the contents (a bit like in Excel). That is much better than the rigid array front elements. It is also much more powerful since cells can be coloured, cell fonts can be changed, cells can be highlighted and still more. Some possibilities appear to lack:


1 There is no 1D version of it. This necitates the user to finely adapt the height to see only one row. This makes that no dark grey line is around it and a user can accidently change to lower lines by selecting a cell and some mouse operation. It is hardly possible to return backward, certainly if the user is not aware that the line is in reality a 2D field.   Under properties e.g.' 1 row, 10 columns' can be given, but that does not prevent changing to other rows. For arrays dimensions can be added (from 1 to many), for the table dimensions 1&2 would be helpful.


2 Cells can be indicated with help of the properties 'selection start', 'selection size' and 'selection color'. The selections can not be programmatically disabled and re-abled when needed. At least a corner element remains if the 'selection size' is reduced to (0,0). With the right-click menu options a 'show selection' option exists for enabling and disabling the feature. It lacks as a property node.


3 Cells can be coloured with help of property node calls, what is nice. The method to undo all colourings and other settings does not exist. The invoke node method 'reinit to default' has no influence on the individual cell fonts, cell colours, etc. An invoke node to reset these features is wanted as well in addition to the existing reinitialisation. This lack is preventing using these features since the changes should be kept in memory somewhere to undo, or all cells have to be overwritten periodically with a lot of code. If the table length is undefined since e.g. measurement data  is put into it, then an arbitrary number of rows have to be assumed. A reset function can take this trouble out of hands.


The same remarks hold probably for the listbox controls.

How many need Delete Option on Context Menu?

Status: New
by Member Naveen2411 on ‎02-18-2015 07:15 AM

For LabVIEW users,

How many of them need "Delete Option" on Right Click Context Menu?

Delete option in Context Menu.png

I feel providing an delete option in right clicking context menu for any Indicator or Control deleting will make developers easy and fast assessable and avoid too-much use of keyboard.

We use our left hand for control and Shift more offen but for pressing delete button which is at right top corner in keyboard, all of a sudden we will remove our right hand from mouse and press Del which is uncomfortable.


So, Developers share your point of view for the same and request to add Delete Option in upcoming version.

Later we will ask even Cut Copy Past...:smileyhappy: He! He! He!

Control + A in Documentation Field

Status: New
by Member Richard_Ha on ‎02-20-2015 05:19 AM

The control C + V work for copying and pasting in the documentation fields, but for some (infuriating) reason the control + A doesn't. :smileymad:

This is a simple suggestion regarding returning all variant attributes from a variant in the correct data type if the name is left unwired but the default value is wired.


As you probably know, if you leave the name and value terminals unwired the "get variant attribute function" will return an array of names and variants for all of the variant attributes. If you wire the name or the default value then the node will adapt and return only a single value with the 'found?' output.


Here is a diagram to show you what I'm talking about:



Currently, if you leave the name unwired but wire the default value this results in a broken block diagram.


The reasons for this suggestion are as follows:

  • Cleaner block diagrams - if you know all of the variant attributes are the same data type then you save the extra constant/variant to data node
  • Possible performance improvements - maybe NI does (or can do) something to improve the performance/memory allocations if the data type is known and can be done within the SubVI
  • I can't see a case where it would break compatibility other than perhaps a broken block diagram would no longer be broken if the default value was wired but not the name but the runtime functionality would remain the same
  • As variant attributes are a very efficient and recommended way of doing key/value lookup tables I think this minor change will tidy things up nicely and if there are performance gains to be had under the hood by doing this then all the more reason to do it!

Thanks for reading and hope you'll +1 my idea!





I started this discussion

and someone suggested to put it here in the idea exchange.

I think it would be great to have a check box in the properties window of an enum control where I can select if the enum control should or not wrap around when clicking the up or down arrow and the top most or bttom most value is reached ( and taking into acount that there may be some values disabled)


Another idea concerning enums is to enable editing the value of each entry. As much as I found out values always start at 0 and increment by one with each entry.


Hope these ideas help improve LabView




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

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:

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.

In LabVIEW 2014, sbRIO-9651 projects need a FPGA socket CLIP to be selected.

This FPGA socket CLIP can be user defined to select aspects like available FPGA pins.


By default, a user defined FPGA socket CLIP is saved in the National Instruments installation folder

or in the National Instruments user date folder. In other words, these FPGA socket CLIPs are not

saved with your LabVIEW project. This means you can forget to keep them by putting them under
configuration control (happened to me when my PC hard disk was changed) and other users will

not be able to use your LabVIEW project if you forget to provide the FPGA socket CLIP used
(happened to me when sharing my projects with NI engineers).


My suggestion is default behaviour of the CLIP generator should be changed.

This tool is used to select or create a sbRIO-9651 FPGA socket CLIP when creating a LabVIEW project.

I propose this tool should always save the created/selected CLIP under the project folder.

This would help to ensure the LabVIEW project contains everything associated with the project.


Optionally, it would helpful if the LabVIEW project dependencies showed FPGA CLIP usage.

I have unknowingly had a project using another's projects CLIP (especially when the CLIPs have

the same name).


"Plot images" for the entire front panel

Status: New
by Knight of NI ‎02-07-2015 12:38 PM - edited ‎02-07-2015 12:39 PM

Graphs have a plot images property that allows us to draw anything we want on the graph area using picture commands. (example 1, example 2).


I propose to have a similar property for the front panel (or specific pane) area that would allow us to address any pixel and use picture commands at run time (e.g. Plot Images.Front to temporarily circle an area to guide the user or place a huge red warning text across the entire panel in case of a malfunction. We could use Plot Images.back to change a logo or show a connection diagram picture, or similar. (currently, we only have the limited background image property)


This should be entirely cosmetic and should not interfere with the operation of controls, etc.


 Here's how it could look like at run time...




When you have to handle events, many times you have to use "defer panel updates"  fonctionnality, in order to make your front panel updates more fluent.


It could be nice to include a checkbox in the event configuration window, in order to ask (or not) an automatic defer panel Update.


If check box is checked :


  • At the begining of the event handler code execution : DeferPanelUpdate = TRue
  • Execution of the event code
  • At the end of the event handler code execution : DeferPanelUpdate = FALSE

DeferPanelUpdate for event handler.png

Compare aggregates option for scalar comparisons

Status: New
by Trusted Enthusiast on ‎01-29-2015 12:50 PM

I would like to have the ability to set the compare aggregates mode for comparisons involving containers (arrays certainly, clusters would be a nice bonus) and a scalar value.  This includes the comparisons to 0 functions as well.



I would prefer to have a feature added to space objects horizontaly and verticaly by value. It would be very helpful for arranging objects in block diagram and front panel. br ws.


LabVIEW Exchange.png

The Report Generation Toolkit provides functions to set various Format aspects of Excel "areas", and Excel Graphs, but doesn't provide the complementary "Get" functions to return the current values.  For example, I wrote a LabVIEW function that will set the Font Color of a row of a WorkSheet to Red (using Excel Set Cell Font), but if I want to find the row with the Red font, there is no "Excel Get Cell Font" that can return the property to me.  Of course, I could cobble something together using ActiveX calls, perhaps, but these are poorly documented, and since NI is already doing the "heavy lifting" to provide the Set functions, it would seem "relatively simple" for them to also add the corresponding Get functions, as well.


Bob Schor  (using Excel as a "controller" for some experiments controlled by a LabVIEW Real-Time system)

Allow more information-gathering tools when on a non-editable VI

Status: New
by Member LukeASomers on ‎01-20-2015 04:23 PM - last edited on ‎01-22-2015 02:37 PM by Member dcarva

I'm looking at a clone. I don't see why I would have to ctrl-M to get an editable version to do such things as:


- get the contextual menu up on the VI's icon to 'find all instances'


- get help on a VI that's on the clone's block diagram


- open or find all instances of a typedef via its contextual menu (the typedef being on the clone's front panel or back panel)

Wire bend issue to numeric nodes

Status: New
by Member Vinal_G on ‎12-05-2014 08:00 AM



As shown in below image we can see that, if I index numeric array and wire it with any of the node from numeric function it gives un-aligned wire whereas as same process if I use Boolean function at output of index it gives well aligned wire.

So due to this numeric function node wire to index out terminal makes our code with full of wire bends which is not as per NI LabVIEW coding standards also.

So here, I want to draw attention for NI, to do some correction to specific numeric function nodes so we can make neat and clean code in LabVIEW.Wire cleanup.PNG

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
Idea Statuses