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
0 Kudos

When i finish my working day I often start to build a installer and execution. Because I don´t want my computer to run the whole night, I initiate a windows shutdown after for example one hour (shutdown -s -t 3600). In this case it would be nice if I could say "Save project and quit LabVIEW after building installer execution" or even "Save project and shut down computer after building installer and execution" so I would not get an error message when I start LV again.

0 Kudos

block reduction shortcut

Status: New
by Trusted Enthusiast on ‎11-27-2014 04:27 PM

As we all (should) know we can expand a block diagram by holding ctrl+l-mouse.

How do you solve it when the diagram is too big? Wouldn't it be great it ctrl+alt+l-mouse removed diagram real estate?

Just like with the expand, everything to the right and below gets moved up the size of the marked box, and in case of crossing structures (like a case structure), it should reduce their size the same.



0 Kudos

Readymade PASS-FAIL button

Status: New
by Member sras on ‎11-27-2014 06:28 AM

LabVIEW has a boolean indicator displaying different colors at T/F condition and alllowing different boolean text entry


In addition, wish to have a ready made indicator with Boolean text PASS (Green Background) and FAIL (Red Background)

All the test applications shall have this PASS/FAIL result and this a quick drop will be useful!

Another common condition is TRUE/FALSE button. These can be added in Silver->Boolean>Buttons section




Typedefs are there but just an idea!



0 Kudos

In the current version of DETT (2014) it does not appear possible to trace into VIs in vi.lib and intr.lib. This is unfortunate since we rely on using development packages deployed with VIPM - and these packages are often installed into the LabVIEW folders in one of this sub-folders. Debugging these VIs can be very useful during development and adding custom trace messaging in the application or to the VIPM packages can be cumbersome.


Ideally it should be possible, as an option, to include or exclude these folders.


Docking Palette/View of open files.

Status: New
by Member OyvindAakvik on ‎11-26-2014 07:05 AM


Having a dockable palette/View of files that are open in labview.


Many developers would probably agree that having 30 VIs open creates lack of order in their desktop, and the way to swicth between them now is by clicking the taskbar icon and scrolling through till you find the one you want (in windows7 - grouped view at least, even worst without grouping with 30++ icons in your taskbar)  


This could be solved by having a viewer, either standalone or even as part of the project explorer. buttons to either see BD or FP before or after the name of the file would also be prefered as having two entires; one for BD and one for FP creates dual entires and is only adding to the mess.






I am taking advantage of the recent FileVersionInfo to pull up the Version Number of the Executable at Run Time and display it for the User (who can then call me and say "Version crashed", and I can figure out which source this was).  I take advantage of the Pre-Build Action to create the Version Number, taking the "Build" part from the Revision Number of the Project itself (since the Pre-Build Action gives me the path to the Project, this is fairly straight-forward).


However, in order to get the correct Build to appear in my Executable, I must build twice.  The reason for this is that LabVIEW apparently reads the Version information before executing the Pre-Build Action, so my attempt to set it to the "correct" value is ignored until the subsequent Build.


Personally, I think it is illogical to have a "build Action" that silently takes place before the user-specified "Pre-Build Action", though there may well be a hidden "good reason" for this.  I would like to request, therefore, that LabVIEW include a "Feature" that specifically allows the Pre-Build Action to include not only setting the Version Information (which it currently does) but allowing this updated Version Information to be used in the current Build.  True, the work-around of "Build Twice, Use Once" works for me, but why should we need to jump through this particular (unpublished and unexpected) hoop?


Bob Schor


Mark selected Connector pattern

Status: New
by Trusted Enthusiast on ‎11-24-2014 06:09 AM

(Unless it's already changed in newer LV's, i'm on 2011 right now)


When opening the connector pattern, the current isn't marked in any way. If i'm after some extra connectors or a symmetrical one (why do people choose 3-1-1-1?) it'd be nice to quickly see where to start looking. A simple bold outline would suffice, maybe in blue?





It is always great practice to make your code as readable and scalable as possible, along with good documentation.  One of the things that get overlooked the most, without even realizing, is having coerced inputs to your functions or VI's.  When you have finished developing a program, it goes through a great deal of review to validate all its functionalities.  Coerced inputs can be one of those issues that can come back to haunt you down the road.  I think having an icon on the toolbar and/or a shortcut keystroke to populate a list of all VI's containing coerced inputs would be a great help with identifying all the necessary functions that need to be examined.

I have the hadit of pressing Ctrl+Shift+S (Save All) which is annoying while working with Read only VIs. We always get a pop-up enabling us to save the VI in a different place or with a different name. As a result we get the browse window to Save the VI with a different name or in different path. This happens on clicking OK (which make sense) but also on click Window close button/ESC key

My suggestion is to continue the save operation only on clicking OK and abort the operation when the user click the window close button/ESC key. This would be more meaningful and would make more sense to the way the Save operation is handled.

I am also fine with adding a Cancel option along with the OK button.







HTML/CSS UI elements

Status: New
by Member Mike_King on ‎11-18-2014 12:19 AM

The web is miles ahead of LabVIEW for its UIs.  LabVIEW should support embedding HTML5/CSS containers as content for VI front panels, that can be bound to any data type or class preferrably to enable more capable UIs.


A modern and capable DataGrid

Status: New
by Member Mike_King on ‎11-18-2014 12:17 AM

How the ideas exchange has existed for more than one project for anyone and not had a datagrid added already is beyond me.  LabVIEW's table is horible, they need to add a proper grid, similar to flexgrid or other common web grids, that has grid sorting, grouping, sortable columns, drag n drop orders, totals, cell editing, cell binding, cell data types, binding complex objects (clusters), themes (CSS formatting perhaps).

0 Kudos

Add ActiveX (ocx) - Controller Builder

Status: New
by Member Tameq-Peter on ‎11-17-2014 09:12 AM

LeCroy oscilloscopes do have a decicated area of the user interface for customization. The custom space can be used by an ocx-ActiveDSO PlugIn that is registred on the instrument.

This kind of ActiveX-Control can do far only be built by some VC and VB compilers.


It would be very nice to build now such a CustomDSO PlugIn for a LeCroy oscilloscope by LabVIEW.


With regards




Tameq Schweiz GmbH

+41 56 535 74 29

0 Kudos

New anchor / mock terminal

Status: New
by Member cyfoo on ‎11-16-2014 11:58 PM



Another feature I wish to see in near future is a wire-anchor decoration or a mock function terminal that could help user prevent wire clutters / overlaps whenever the diagram cleanup is performed.


Kindly read the attached pdf for details. Please consider and many thanks for reading...




Filter dependencies from "Find Items with No Callers"

Status: New
by Active Participant dan_u on ‎11-13-2014 07:17 AM

"Find Items with No Callers" could be a useful function on the project, but currently most items it reports are in Dependencies. Why is an item even under Dependencies if there is no caller? It seems if I call one function from an .lvlib the whole library is in dependencies, and all other functions have no callers. This floods my "Find Items with No Callers" window with useless entries.



Suggestion: add option to hide items from dependencies in the "Find Items with No Callers" window (or even hide them by default).


0 Kudos

Loop conditioned by a list of boolean variables

Status: New
by Member logatto on ‎11-13-2014 05:35 AM

Hi, in large application where you have many parallel loops you must to be sure to put for all of them the correct out condition (even for "For" loop if they are long). i.e. in case of error or when user press "Stop" while the program is running.


I think could be useful if you can define somewhere a list of boolean variable and when you place a loop in the block diagram it is automatically connected to the list of boolean variables. For that particular loop you can select wich variable (one or more) defines the stop condition.


To select the variables you could use the same approach used for  "Timed Loop".


The list of variables should be linked to the project and active only for that project.




New structure (VI-less subVI)

Status: New
by Member cyfoo on ‎11-13-2014 04:28 AM


One feature I wish to see in near future is a new structure that consolidate part of the code into an icon, just like creating a subVI, but does not necessitate the creation of a VI external file.

Kindly read the attached pdf for details. Please consider and many thanks for reading…



0 Kudos

VI Properties Improvements

Status: New
by Trusted Enthusiast on ‎11-13-2014 03:17 AM

Below are some of the improvements I could think of reg VI Properties. Hope these are not posted elsewhere in the Idea Exchange (did a search, but got different results). :smileyhappy:


  • Make the VI Properties window non-modal & allow it on multiple VIs at a time. Include the VI name in the title bar (I saw a similar idea, so including it here).


  • Or/And, allow multiple VI Properties windows to be opened & configured at a time, at least across multiple projects, if not feasible among multiple VIs within the same project at a time. Now this is possible only if you open multiple instances of LabVIEW (of same ver) to open your different projects at a time.


  • When we rt-click a SubVI & select Properties, the least we expect is to see its Label property. Change this context menu to VI Properties (if the rt-click is on a SubVI), or change the behavior to invoke the VI Properties window by default when rt-clicked on a SubVI. Countless times I have been annoyed by this feature. Why would someone need to physically open a SubVI to check its Properties?


Any comments/takers... ?

I would find it extremely convenient to have a notification option (or options) to notify the user when the Build Status for a project is complete. 


Sometimes when building executables or installers--or both--the compiler can take a while depending on the size of the project.  During this time I don't just stare at the progress bar, but found that even if I left window open in plain view (off to the side or something), it is not obvious when the process is complete (the 'Done' button changes to Enabled and that's about it).


Options to notify the user could be any number of things:

  • Beep when complete
  • Bring the dialog to the front (only works if it's not visible already)
  • Flash the window on the taskbar as a notification (maybe)
  • Pop up a modal dialog
  • Some combination of the above
  • Also possible, a checkbox on the Build Status dialog to receive a notification or not
0 Kudos

XY graph palette

Status: New
by Member VladimirP on ‎11-10-2014 11:07 PM

I am missing plot color palette selection. Standard Color set for multiplot graphs is good for black or dark background, not for white. One of automatically generate color is white.

0 Kudos

Inconvenience with quick connect

Status: New
by Member HarryYang on ‎11-08-2014 10:45 PM

I know "quick connect" is a new feature with Labview. Labview would choose to connect the newly added block to an adjacent receiving block automatically.  But I am encountering some minor inconvenience when using it, expecially when there are multiple receiving blocks close to each other. This feature is actually making connecting procedure more complicated. As the chance of the newly added block to select the correct block to connect is small, corrections need to be made each time, which made connection even more time-consuming. I would recommend doing something similar to Simulink, where you select the ports you wish to connect while holding down some hotkey (say ctrl or shift) to quickly connect two adjacent blocks.


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