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

update value within array of cluster

Status: New
by Member r_exler on ‎08-31-2015 10:17 AM

Updating a value within an array of cluster is too complicated compared to other programming languages.


In my application I hold an (global) array of jobs to do, each consisting of its name and an array of (different) parts belonging to this job. One element of the part's description is the number of parts already done. If I want to update this value, the code looks:



Note the calling function has to update the global variable after updating or JobFilesIn and JobFilesOut can be replaced by reading/writing the global which does not make the code more visible.


Within C code the update would look


which will not raise the need of making it a function (VI) at all.


A solution might be similar to Replace Array Subset if the compiler is parsing the data type on the input and accepting indices and cluster element names as shown below


Of course this should work with any data type selected from the initial variable by the selectors similar to C code




It also should accept a cluster as top level element as well, e.g. to replace an element within an cluster of clusters similar to C code



or an element within an array which is part of a cluster.



All the C code examples above expand to LabVIEW code which is hard to read.


Add Copy/Paste to Quick Drop selection

Status: New
by Trusted Enthusiast on ‎09-02-2015 09:19 AM

In some cases, it would be very useful to be able to copy and paste the text of the selection box.


QD Copy Paste.jpg

Allow comments to be added in runtime

Status: New
by Member TimBotsM on ‎08-31-2015 05:21 AM

Although it might be tricky to implement I would like to suggest the option to add comments to a block diagram while the code is running.


This way you can make notes to the block diagram for debugging and/or "reverse engineering" (examining LabVIEW spaghetti for example).

Inserting the Error case in the Error wire

Status: New
by Member patibandla on ‎08-29-2015 01:38 AM


Problem: in some of the code we need to insert the error case. it will take time to create error case and wiring to it.


solution: if we can able to insert the Error case in the Error wire , it is easy to Error codes insdide the case.

Inserting Error Case.png

Event Structure: Configurable timeout terminal

Status: New
by Member MGiacomet on ‎08-20-2015 08:18 AM

Tired of resizing an event structure and having to relocate the timeout constant?... Simply double-click on the hourglass and type the timeout value!


Of course, the option of wiring to the event structure timeout input should still exist. Just like the timed loop, where you can double click and set the period, etc.




Resize Rearrange Cases window

Status: New
by Member pawhan11 on ‎08-20-2015 10:41 AM



Could You allow to resize Rearrange Cases window? 




By default it fits only 8 cases and it is hard to move and work with it when we have to rearrange 30 or more...

Other idea is to select many cases by holding Shift

Implement Symlog scales

Status: New
by Trusted Enthusiast on ‎08-22-2015 02:58 PM

Graphs allow displaying data in linear or log scale.

This doesn't go without glitches, so my first suggestion would be fix all the annoying bugs which exist.

But a common way to get motivated to fix a bug being to implement a few feature, here is a unique opportunity:


Implement symmetric log scales (aka symlog scale) on all Graphs


What is a symlog scale, you will ask?

It is a log scale accepting negative arguments.


If x > 0, then Log(x) is computed (and labeled "x", hence the log scale apparence).

if x < 0, -Log(-x) is computer and labeled "x"


To get a visual representation of what this all mean, Google "symlog scale" and you will most likely end up on this page from which I am linking this figure:



Of course this should work on both axes (or all 3 axes for a 3D Graph).


The benefit is that when a curve has negative values, using a log scale to represent the plot results in a clipped plot. All negative values are gone, leaving gaps in the plot. The only way to visualize them is to revert to a linear scale, which now clumps all small positive values to pretty much the same location on the axis.




I faced to delete multiple elements form the array which is having 20 steps.



if able to select multiple elements by holding the shift key we can delete selected items 1 time and can insert 1 time.



Array element.png



Silver Error Cluster Boolean

Status: New
by Knight of NI Knight of NI on ‎08-03-2015 10:22 AM

I have a Red-Green colorblind coworker.  When he looks at the Silver Error Cluster, he actually cannot tell if there is an error.  Why?  Because NI decided to make green the false state and red the true state of the boolean.  So he updates his error clusters to use black for the false state.


Simply put, that boolean display needs either icons (like in the Modern Error Cluster) or different colors to help these people.

Edit / Find and Replace (coercion dots)

Status: Duplicate
by Trusted Enthusiast on ‎08-22-2015 01:53 PM



                                                     Be able to find the " coercion dots "




NI send us the NI Developer Suite each year on DVDs all packed in a nice little NI branded dvd carry case. We are on the SSP suscription and we receive 3/years, which means I have a whole stack of them.


I suggest that NI start shipping USB keys instead. USB has several advantages:


  • USBs are smaller
  • USBs are more usable on devices without DVD player
  • Installing with one large USB means no more DVD swapping. I can go to lunch while NI installs/updates without having to change the DVD every couple of minutes.
  • USBs are reusable: when you get a new version on LabVIEW on a new USB, you can use the old one for regular usage. This also means less waste, since the USB keys are still in use after a new version ships, but the DVDs are useless.


Ship developer suite on NI USB keys

Status: In Development

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.


I recently starting putting String Indicators in some of my programs that identified the Routine, along with its Version Number.  I have also created Dialog Boxes with one-line Messages, usually in large size, often Bold, sometimes colored and with a colored background.  I wanted to have the String indicator displaying these one-line messages "fit the text" (if the indicator was too short, the message would be truncated, and if too long, it "looked unprofessional" and wasted space).  I found code on the Forum that was awkward and didn't scale with fonts -- I found a work-around, got in touch with NI to inquire about filing a CAR to fix the specific flaw in their Get Text Rect function that I discovered, but was told they were not interested ("You just need to add a constant").


After more investigation, I found an even better solution to this problem, which I have posted to the LabVIEW Community here.  While this seems to work, I would like to propose that NI provide a simple Method or Property that could be used to scale the horizontal size of the contents of both the String and Path controls to just fit the content to be displayed in these controls.  This Method or Property should work regardless of the other properties, such as Font Size or Font Attribute (Bold, Italic, etc.).  It should also work regardless of the "family" of the control (Silver, Modern, Classic, or System).   I do note that System Strings might be a problem, but I could get my code to work with the System 2.0 String indicators available on the LabVIEW Tools Network.


The figures show a Front Panel with "too small" indicators truncating the display of their (variable, and run-time-dependent) content, plus the same Front Panel after I run my "Size-to-Text" code on the indicators.  I'm suggesting that NI provide a Method/Property to do the "dirty work" for me.


Notice truncation of Text and Paths


After programmatic adjustment of Indicators to "fit" their content.


Bob Schor

error case default wire settings

Status: New
by Member patibandla on ‎08-29-2015 01:42 AM


problem: inserting the default  control setting in the Error case


Solution: in the case if we can able Create Error Case Defaults.PNGto insert all the default setting at one time.

Picture says it all.


Concatenate with an option of 'concatenate to new line'



I am not allergic to Kudos, in fact I love Kudos.

 Make your LabVIEW experience more CONVENIENT.

Free Labels to Block Diagram Constants Conversion

Status: New
by Member patibandla on ‎08-01-2015 02:37 AM - last edited on ‎08-03-2015 12:50 PM by Community Manager

single click we can create Lable in the Block Diagram.

if we want to create constants(sting , enum,numaric etc), it will take three steps.


by converting the Free Labels to Constants, I feel it is easy way to create Block diagram constants.

Free label to constant.jpg

Path Control Disable Text Entry

Status: New
by Trusted Enthusiast Trusted Enthusiast on ‎07-07-2015 12:12 PM

If I have a path control on my front panel for the user to interact with, I will always show the browse button.  This button makes selecting a path easy from a user perspective, and from a developer I know that the path they selected has some level of validity.  So for instance I know that the path they selected must exist and be a valid path otherwise Windows won't let them select it, and the value change won't be triggered for the control.


But the user can manually type in text into the path control, and when focus is taken off the value change event will take place.  The problem with this is the path they entered might not be valid, or may contain characters my platform doesn't support.


I doubt a user will manually type in text in the control often, they will use it as an indicator showing the path they selected using the browse button, but on the off chance that they type somthing and it isn't valid, my code might crap out throwing errors.


I can add code to check for a valid path, and I can add code to check for illegal characters in the path, but I'd have to do this for every path control on every UI the user sees.  I could also write an XControl for this with a decent amount of work and hopefully meet my needs, but it would be nice if this were a native feature.


So what I'm suggesting is that the path control have an option, possibly in the browse options dialog, which makes the interaction with the control, only available by using the Browse button.  This would ensure that any value change event will be from the user picking a valid path with the browse button.

Allow project explorer window to be pinned

Status: New
by Active Participant ToeCutter on ‎06-29-2015 05:58 AM

I have a large library of general purpose functions and I do a lot of OOP in LabVIEW, and as a result my preferred workflow involves dragging a lot of functions from the project explorer window onto the block diagram. This workflow is slowed down, however by the fact that the project explorer window is regularly hidden by other windows when I click on them.


What I would like to see is something like most development IDEs have, e.g. Visual Studio, where I can have the project explorer always visible in a fixed position on the screen. I suggest this would be an option, so would not affect those who like things the way they currently are.

View and modify splitter hierarchy

Status: New
by Active Participant dsavir on ‎06-17-2015 03:01 AM

I use Splitter extensively to create resizable GUIs. However, if I create my resizable GUI and then my customer asks me to add parameters in a new pane on the left, I can't add to an existing GUI a splitter in the top of the hierarchy, i.e. a new vertical splitter that all the existing splitters will be on the right of the splitter and a new empty pane on the left. Any splitter I add will be added to the bottom of the existing hierarchy, and there is no way to change this. So to do this I basically need to rebuild the GUI again from scratch.


Another example, if this is my GUI:


I can't add a status bar now, as any horizontal splitter I add will be inside an existing pane, and this can't be modified. However, if this idea were implemented, I could View splitter hierarchy and create a new horizontal splitter at the top of the hierarchy so that I would have my status bar without rewriting the whole thing.






Project path visible in the Title Bar

Status: New
by Trusted Enthusiast Trusted Enthusiast on ‎08-13-2015 09:32 AM

We have a software product where we have started working with branches and sometimes have a few different versions of the repository checked out for code implementation / testing / exploration.


It happens that I have two (or even more) versions of projects with the same name open at a time from different paths.  Currently I switch to files view and back to check which version I am currently looking at and I just thought it would nbe nice to see the path of the project file int he title bar of the project window.


I know I can the project, I know there are other ways to get this information but can't we have a simple indication as to the path at least SOMEWHERE in the project window?

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