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

View >> Gigantic Coercion Dots (now with a variety of colors)

Status: New
by Trusted Enthusiast ‎11-30-2010 09:29 AM - edited ‎11-30-2010 09:37 AM

We have (collectively) complained about coercion dots many times on various LV forums -- they are nearly invisible and there are three different kinds, which require different levels of concern. The problem is that there are very few pixels within a terminal and there's no space for any pattern to differentiate the three kinds of coercion (and changing colors is a problem for reasons discussed here in the Idea Exchange).


Another LV developer had an idea that I liked: add an option to view giant coercion dots. We have avoided this because coercion dots bigger than the terminal would interfere with wiring. However, many developers have a policy of eliminating all coercion dots on their diagrams. For those who have such a policy, they could eliminate the coercion dots as they work, and thus might not see any problem from such large dots. Large dots would solve lots of other usability problems that coercion dots have today.


This option could be something in Tools>>Options, but I'd rather it be something in the View or Edit menus so it can be quickly toggled on or off with a shortcut key.


These graphics are "programmer art" -- I just made the three dots look different. Please sumit alternate images for the three dot types if you have better style suggestions. I did make the three dots differ in both pattern and color so that we avoid problems with colorblindness. The type-only was a solid dot, the widening coercion is a bulls eye, and the narrowing coercion is a single ring. Any redesign should definitely take colorblindess into account.



I use the In Place Element structure a lot.  95% of the time it's to work with private class data, but occasionally I use it for other things too.  I get tired of having to navigate the context menu all the time just to add the IPE node I need.


When I'm stringing a wire to an IPE structure, it would be nice if there were some way to have the structure automatically inserted the correct node type and attached the wire to it.  Personally I think ctrl-click on the IPE border when a wire is attached to my cursor would be a good shortcut key for this functionality, but I'll leave implementation details up to the experts.**  Most of nodes work with only one "kind" of wire.


Current IPE border nodes:

Index/Replace Array Element

Split/Replace Array Subarray

Unbundle/Bundle Cluster or Class

Unbundle/Bundle Waveform

To/From Variant

Read/Write DVR

In/Out Element (Void)


If I have a class wire and I ctrl-click on the border of an IPE indicating that I want to auto-insert a border node, there aren't a lot of choices for what kind of nodes will work with that wire.  Same with variants, clusters, and waveforms.  If the wire is some other data type (such as a string) have it insert an In/Out Element node.  The only place where some ambiguity exists is when attaching an array.  Should it insert an Index or a Split node?  I use Index more than Split, but I'll defer to the usability experts an NI again.  They should be able to devise a good way to choose between the two options.


(**These kinds of features often meet resistance because magic button clicks aren't easily discoverable.  I agree that is true, but the original functionality of right clicking on the structure *is* discoverable and will remain.  I do not agree the lack of discoverability is sufficient reason to not add magic button clicks for power users.)


Find "Coercion dots" in LabView project

Status: New
by Active Participant manu.NET on ‎11-26-2010 09:43 AM



The "Coerce dots" are handled by LabView as Visual warnings ... but a bad type coercion could have very bad issues ! :smileymad:


It should be nice to be able to find all "Coerce dots" in all the VI's of a project, in order to check if they are critical or not.







when I have to rework a vi, i usually start by putting the existing code in a disable structure

and then start working in the disabled 'case'.


Quite often I end up trying to replace the disable structure with a case structure to test the new or reworked vi.


Now I have to copy everyting into a temporary vi, remove the disable structure, put a case structure in place, paste again and rewire iputs and outputs.


Please add the ability to replace the disable structure with a case structure.



It will be very helpful if you can add a method for table control to enable or disable a particular cell with given row and column number.


By default, row and column numbers for that method should be -1.


If user specifies only row number with out specifying column number, then that entire row should be enabled or disabled based on user input. Similarly, if user specifies only column number without specifying row number, then that entire column should be enabled or disabled.


Hope this helps.




0 Kudos

I would suggest that NI makes the datatypes of the "Quotient and Remainder" VI consistent.


If you now wire a double to the VI the outputs are of the datatype "double" however in my opinion this is not consistent with the mathematical definition of quotient, floor(x/y) and remainder, x-y*floor(x/y). The output of the VI is always a integer and should therefore also be of that datatype, thus one of the following datatypes (I64, I32, I16, I8).


Setting Run-time Position for a Modal Window

Status: New
by Member Seamus_C ‎11-25-2010 06:42 AM - edited ‎11-25-2010 06:45 AM

When setting developing an application that uses a Modal pop-up window it can be very frustrating when the pop-up appears on the monitor you are not looking at.

In the VI properties you can choose the position and you can choose which monitor to use as seen in the attached .png.   


It would be great if we had an option to choose "application montior" so the Modal window would appear where ever your VI or exe is running.






Drop the pane hierarchy

Status: New
by Active Participant Mads on ‎11-25-2010 04:59 AM

When you create multiple "panes" in a front panel - e.g with the use of splitter bars or tab controls - LabVIEW has a "smart" function that sorts all the controls and indicators by pane when it needs to display a list of the available controls and indicators. The problem with this however is that even with a very low and probable number of panes the resulting hierarchy becomes unwieldingly large.


Figuring out which pane you are looking for becomes a pain. If you have not named all your splitter bars e.g. (which most likely is the norm) it gets really frustrating to search through the contextual menu.


So - my suggestion is that the hierarchy is either dropped or that you can choose to do so in the LabVIEW options (after all, even with 50 controls it would be quicker to scroll through a flat list than to hunt through the hierarchy first)..or that it is only used after a certain threshold for the number of controls.


A third option might be to visualize in the menu itself where on the front panel the different panes are located...that way you will know which is which event though you have not named each splitter etc...


hierarchy problem.gif

Time to time I using this menu for setting values to defaults. I put some strings or values into some controls, then select following menu:




The problem - when menus selected second time - item still active, and I'm slightly frustrated - is my current values already defaults or not? I select this again and again...


Suggestion - when current values are equal to defaults then this menu item should be gray (as menu Cut Copy, etc on screenshot above).


The same with Reinitialize Values to Default. What happened when this item will be selected? 


This slightly related to this idea, but I would like to post this idea separately.

This also can be classified as light cosmetic bug (because when menu called second time, it does nothing in general).

Also when VI just opened - this menu should be grayed - then this fact can show, that current values are equal to defaults.





(Reasonably) equal treatment for OS X (please)

Status: New
by Member Dale_Chayes on ‎11-24-2010 05:44 PM

While NI provides (thank you) reasonable support for OS X these days, the support for installs and updates "on line" are very far behind those for Windows.


For instance, there does not appear to be any option to download Labview 2010 for Mac but I can for Windows.



When using a case structure within a loop for a state machine, or when using an event structure, it is frequently necesary to either add a new case/event or add a new state variable to the structure.  This can lead to unexpected behavior if the user has accidentally used "Use Default If Unwired" on an output node, and will require time consuming wiring of all cases otherwise. The Linked Input Tunnel Option helps with this.  However, the mass of state variable wires, if there are several, still creates a confusing and cluttered diagram.


It would be nice to add a "Feed Through if Unwired" option.  This would allow us to wire ONLY the variables that need to change, and only need to examine the relevant cases.  Additionally, you would get a nice clean diagram.  Here is one idea, shown for an Event structure:


NI Shift Reg Suggestion_sm.JPG


allow user created growable functions

Status: New
by Trusted Enthusiast on ‎11-24-2010 11:49 AM

Many built-in functions have the growable ability. Essentially a function that accepts an array of data in scalar form, this saves the step of building an array prior to wiring a terminal.  I would like to select any  1-D array on a connector pane and mark as growable.  Then when the vi is used as a subvi, the icon would have the growable ability.  This could have been used as for example for making a growable error handler or implementing new compound math functions.  I know this is probably hard to do and might be possible with xnodes but I dont have time to learn this.  It is useful for making reuasble toolkits which look more like the native G functions

It would be useful if we can access the plot color and point color separately on the plot legend itself as we do in the properties dialog box of the graph instead changing it by toggling the space bar


graph plot legend.jpg.


Run as Administrator Option for System Exec VI

Status: New
by Member srdfrn on ‎11-22-2010 05:23 PM

It would be nice to add another dimension to the system that gives the user the option to open up the “Run as Administrator” command prompt in Windows 7.  This would enable a system administrator to use LabVIEW to make certain, currently restricted, changes to the computer.  I don’t believe it would create a security risk because you have to be logged in as an administrator anyway to have the access rights


As far as I’ve seen, there really is no string that you can enter into the command line that will instruct an elevated command prompt to open.   With this added functionality in the system exec vi, however, you will be given more flexibility with what you can do through your LabVIEW program.




Navigate with arrow keys in dialog boxes

Status: New
by Member schrotti on ‎11-22-2010 11:17 AM - last edited on ‎11-22-2010 01:09 PM by Active Participant Laura F.

It would be nice if we can use the arrow keys to switch the key focus between the buttons of the dialog boxes which for example appear if you close an unsaved VI. I don´t know how it works in Linux and Mac OS, but in Windows the most dialog boxes support that.

0 Kudos

It would be nice to have an option in XYgraph that could allow the user to define some set of spatially related points (or cluster in statistics) by drawing some boundaries with complex shapes using the mouse. Here is the problem that brought me to write this post. Let's say that we have a series of data {x1,x2...xi...xn} that represents the duration of time between two adjacent heart beats. The pointcare plot is the representation of the points [xi,x(i+1)] and that can be achieved to by the XYGraph function. Using this graphic, it is expected that adjacent intervals with almost similar values will form a cloud (circular, eliptic or with more complex shapes) centered around the average values of the xi. Now, unusual changes between adjacent xi values in the time series (lower or higher x(i+1)) will result in points outside of the primary cloud. This is an easy way to identify abrupt changes in a time series.


The step I'm blocked with the following. After I used the XY graph to plot the [Xi,X(i+1)], I would like to use the mouse the draw the border of the primary cloud and extract separately the indexes of the point in or points outside the border. 


Again, I really appreciate your help for that.




Automatic Coersion Handling wherever possible

Status: New
by Member Nandagopal on ‎11-22-2010 06:51 AM

It would be nice if LabVIEW handles the coersion automatically by inserting the required conversion function with inserted function in different color or in any other representation wherever possible so that user understands there is a coersion happening and in the same case we will not have performance pitfalls. Example scenario is show in the picture.




If the user still want the coersion, there can be an option of "Forced coersion" in the right click menu of the inserted function.



It would be nice to add a new menu item in Labview IDE, which could close all executing VI's.


This could solve the problem of "running Modal VI's" which can "block" an execution.


This could also be helpfull to "clear" the execution context when you have bad closed "detached and assynchonous executing VI's".


The top, would be to get a report (a list of VI's in a window) of the forced closed VI's ... It would be helpfull for analysis.




Cancel Button on Save All dialog

Status: New
by Active Participant Jim_Kring on ‎11-21-2010 03:46 PM

Sometimes I select File >> Save All accidentally when I mean to just do a File >> Save.  I really wish there were some way to press Cancel/Abort so that it would stop wherever it is in the process.


Include JKI State Machine in Templates

Status: New
by Trusted Enthusiast on ‎11-20-2010 07:06 PM

Ok this idea would be trivial for NI to include in 2011.Heck I could do it.


The idea is simply to include the JKI state machine in File/New/Design Patterns. It is BSD code and I am sure that JKI wouldn't mind anyway.


I must admit that I have an ulterior motive. If this were included in the NI distributed templates then I could use the JKI state machine for my CLD exam. And so could you!


Now let the kudos start rolling in so NI will take notice.

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