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

wire jumping across case structure

Status: New
by Member JimboH on ‎08-14-2009 11:11 PM

The idea is to be able to replace wires running across a case structure with terminals that take the connection on the left side and connect it to the right side.  I would think the left side should allow a through wire for reading variables, but the right side should not, as then the jumping structure wouldn't really be needed.  This is something that would be specific then to that case or entry in the structure, and not the structure itself.



When you have a lot of cases (or events) in your case (or event) structure it can be tedious to go back and forth between them (yes, Ctrl + Mouse wheel works great but can be hit and miss to get to the right one that is many cases away).  Often times I am in one case, I need to grab/do/look at something in another case and then return to the case I am working on.  It would be nice to have a Back and Forward button (similar to a web browser) so after I can quickly jump back to where I was.  The only way to do it now is to click on the case titles, scroll up/down (which can be very tedious if you have enough cases that it goes off-screen) to switch between.


Status: Declined
by Trusted Enthusiast on ‎04-10-2012 06:24 PM



                  I would like to be able to program the XNodes.





          Include the programming of Xnodes in labview features


                               ... for the next Christmas   clin d'oeil _ 1.gif





Status: Declined
XNodes are a proprietary technology that NI will not be releasing to the public


I have several Labview versions, and some files are in 2010, others in 2011.

I often work with both version launched, and when I want to open a file, I have to do File=>Open and choose the file (with the good Labview version). Opening a 2010 file with both version 2010 and 2011 launched open my file with 2011, whereas it has been saved in 2010... (maybe a bug ?)

I would appreciate if I could drag and drop the file I want to open on the LV icon on taskbar (+1000 to the following idea : here)

Best regards,

Within the Project Viewer it is possible to create virtual folders in which to help you organise your VIs. Why is this feature not available in the "Build Specifications" area below it.

The main project I am using has 15 different items here, most are grouped (I have a .exe and a .installer for each variant of the software I am creating). It would be nice to group these in folders as my project is getting messy.


Cheers, Alec

I find that changing of the color of the axis name to be different than changing the colors of any other items on the axis of a graph or chart as well as less intuitive and more mouse intensive.  If the ability were on the Scale page of the Properties, it would be with the rest of the axis Scale color boxes.


Here is the current Scale page of the Properties dialog box for a graph:

Graph Scale Properties Page.jpg

So you can adjust the colors of the scaling like so:

Graph Scale Properties Color Changed.jpg


But the only way to then change the color of the axis name to match the scale colors is to highlight the entire text box, click on the Font drop-down box, slide to Color and then slide to your color without moving the cursor outside of the drop-down box because then you get to start over at the drop-down box.  This is a lot of mouse movement when you have three or four different plots that you want to have unique colors.


A better way would be to have a selection for the color right on that properties page like so:

Graph Scale Properties Page - Revised 2.jpg 


It doesn’t matter if it’s in that spot exactly or with the rest of the color selector boxes in the Scale Style and Colors section.  But I believe it would make sense for it to be on that page.

This is more of a bug report than an idea suggestion (although the boundary between both is sometimes tenuous).

When creating a Formula Node input or output variable, the name of a control or indicator created by Right-clicking the terminal is "input variable" or "output variable":




It should be named after the variable it is connected to. In the example above, I would expect "delta".

Shouldn't be difficult to do, the Mathscript node does things right:




PS: don't tell me I don't need to declare the output variables in the formula node. I know. I just created the latter for debugging purpose, which reminded me to post this overdue bug report.

Status: Completed



When you have to work with multiple LabVIEW projects at the same time, you may point to a VI of the second project, or save a VI in the other project ... This occurs frequently when you have to work with a project template which you have to duplicate !


The problem is that your project works fine ! But you point on misplaced VI's !

The problem will only be seen when you have to give the project to someone else, or 2 or 3 year after the project completion, when you want to made some updates. And then AIE ! A VI is missing ! :smileymad:


It should be nice to generate an "Optional"  warning (Popup), when any user action (save, insert VI on front panel ... ) handles with a VI not located under the project path. 

This visual warning could be interresting to avoid this kind of error.



It would be great if you could create a comment that would stick to the case selector label in a case structure.  If this were implemented, in the screenshot the "5PLL" comment wouldn't fly off to a random place when I cleaned up the diagram, but would stay with the case selector, making the code easier to read.



Add New... to the RCM in projects

Status: New
by Proven Zealot on ‎04-05-2012 09:09 PM

OK, I've been working with some reformed txt programmers.  They like to decorate their vi names.  i.e ""  I've just about convinced them that the fully qualified name of " on Giszmo" is better but, it is not quite what they are looking for.


My Ctrl+Shift+T keyboard shortcut Launches File>>New...  Because it is not available from the RCM when selecting a folder in a project.  So if I select Funct.vit templates, create the vi and save it as Do Action in Giszmo project.  The displayed FQM is "Funct Do Action on Giszmo"


Perfect decoration!- since Funct(X).vit and Funct(y).vit tell me what type of action I indend to do! 


Here's where the story turns sad.  When I select a folder in a project and "Ctrl-Shift+T" the new vi is added to the project at root- Not at the selected folder.


This one seems like a no-brainer!

Adding last column number to Excel Get Last

Status: New
by Member mfattahi on ‎04-05-2012 07:51 PM - last edited on ‎04-06-2012 09:06 AM by Member MaryH

Currently NI_Excel.lvclass:Excel Get Last gives the last row in an excel worksheet. I am suggesting to add a last column count as well to the same VI.


Current NI_Excel.lvclass:Excel Get Last






In existing "File Dialog" Express VI- configuration Dialog we can specify what we want to select(File/Folder), wheather its new or existing File etc.

However for specifying File Pattern, Pattern Lable, Dialog name etc. we must connect constants from outside. it takes lot of space.

it would be great if those options can be configured from pop up.

Also need a multiplier property node for the scales as well.


Not sure why this would not have been done yet, and not sure why it took me 20 years to suggest it either.





Add Comment "Bubbles" option

Status: Duplicate
by Member Matt B on ‎03-30-2012 02:27 PM

Properly commenting labview code is very important and also very cumbersome in labview.

Currently, text boxes are used to comment code, but the occupy valuable space in the block diagram, which also limits the amount of text you'd want to put in the box.

The text boxes also need to be moved/resized when things change, which is also time consuming.



each labview object ( case structures, variables, bools, etc...) could have an "enable comment bubble" option.  When you mouse over the object, the comment bubble

would appear.  This would allow large amounts of valuable information to be presented to the programmer without destroying the value of seeing the code layout without comments.

Properly commenting LabVIEW code is very important and also very cumbersome in LabVIEW.

Currently, text boxes are used to comment code, but the occupy valuable space in the block diagram, which also limits the amount of text you'd want to put in the box.

The text boxes also need to be moved/resized when things change, which is also time consuming.

Each LabVIEW object (case structures, variables, bools, etc...) could have an "enable comment bubble" option.  When you mouse over the object, the comment bubble

would appear.  This would allow large amounts of valuable information to be presented to the programmer without destroying the value of seeing the code layout without comments.


For example,


See Fig1.jpg


All the comments on the above VI could be associated with a particular object.  There could also be a “show all/hide all” option to quickly view all comments in the VI.


See Fig2.jpg



Mousing over the red-triangle (or whatever the comment indicator looks like) would result in the comment showing up:


And then disappear again when the mouse is moved off it.  The position of the comment box could default to a certain off-set from the indicator, or even better, the comment position would be configured by the user when the comment is created.


See Fig3.jpg



Status: Duplicate

Block-Diagram Shortcuts / Links

Status: New
by Member iannicholson on ‎01-10-2010 07:13 PM

An object on the BD that, when double-clicked, would take you to another location in the BD. This would be useful when you have several areas in case-structures, sequences, or event-structures that you would like to document in a central location.


In particular, I have a case-structure that shows windows to the user. I have a specific window that I need to be modal, so I open that in my main event-structure instead of the window control loop. These two sections of code accomplish a similar task, so it would be nice to add a link the event-structure case near the case-structure. This would make the event-structure case easier to find.


Another way to accomplish this could be to extend Rick K's idea ( to allow the hyperlinks in comments to link to specific cases or BD objects.



My customer has a big LabView project with many destination definitions in build specification. It would be nice to have a possibility to sort the destinations in alphabetic order in future LabView versions.



Make Nguyen

Finland Technical Support.

draw rotated text on picture

Status: New
by Member safar on ‎03-29-2012 11:02 AM

on picture control only we have 4 direccion  to darw text on this control , i see is necesary to change the control text orientation to float variable which is the angle of rotation on the text. 

This is so obvious that it must have been addressed before, so my apologies to those who must have seen this suggestion in the past!


The Event structure is only specific down to the "Menu Selection (User)" level. This is certainly useful, particularly if several VIs share common menu items, as this event handler can just call a generic subVI to handle them.


In many of my own designs though, some of the Menu events will duplicate the functionality of front panel buttons (for example: a "Do Something" menu selection, plus a "Do Something" button that does the same thing). It would be useful to have a more specific user menu selection event - in this case, one which trapped the "Do Something" menu selection. Ideally, the general "Menu Selection (User)" event should filter out items which already have specific handlers assigned to them.


Expanding a bit, it would be useful for this event case to also handle the "Do Something" button press. In LabVIEW 2011, if I add a button handler event to an event case which already handles a user menu selection, I lose the ability to select an "ItemTag" in that event case. So now I have to factor the event handing code into a subVI in order to avoid code duplication, which may be inappropriate granularity for simple handlers.


Again, my apologies in advance for suggesting the obvious!

CTRL+drag terminals

Status: New
by Active Participant Zafer.Depe on ‎01-17-2011 07:54 AM

 I have searched but couldn't find any idea about that. At block diagram, if we ctrl+drag any variable Labview creates a new copy of the same object but when we ctrl+drag any terminal it creates a new object (terminal). I rarely create a copy of the terminal from block diagram. Sometimes if the code is really huge and you put a terminal inside the code without being noticed when you drag that code it becomes hard to clear new terminals. I think it would be better if Labview creates the local variables of the dragged terminals. Front panel action and ctrl+C - ctrl+V should stay same.




























Currently when you look in a project file the context help only changes when you move the mouse over a new item.


It does not change if you select an item in the list and then use the up and down cursor keys to move to a different item.


IDEA: Update the context help when a new item in a project file is selected using the cursor keys.

Status: Declined

Filed as a bug report (see previous comment)

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