LabVIEW Idea Exchange

Community Browser
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!
cancel
Showing results for 
Search instead for 
Did you mean: 

Do you have an idea for LabVIEW NXG?


Use the in-product feedback feature to tell us what we’re doing well and what we can improve. NI R&D monitors feedback submissions and evaluates them for upcoming LabVIEW NXG releases. Tell us what you think!

Post an idea

I find it a real pain to add simple formatting to text in labels and decorations (free labels / floating text).  I really wish that Ctrl+B (Bold), Ctrl+U (Underline), and Ctrl+I (Italics) would do thier expected magic.

Allow probes to be added to unwired signals, E.g. interation number in FOR/While Loops, unwired subvi outputs, etc....

It would be nice to have bookmarks (possibly based within the project) so that you could quickly jump to certain areas of your code that has to be modified or reviewed frequently.  Obviously, things like state machines are self documenting, but it would still be great if you could quick jump to certain areas.  Being project based, you could also jump to any bookmark in a subvi.

 

bookmk_menu.PNGbookmk_diagram.PNG

How about retaining the undo history after a VI has been saved? 

 

I have noticed in some places in the LabVIEW IDE that the selected attribute is not properly highlighted. A perfect example is Cursor Attributes on a Waveform Graph:

 

ShowAttributeSelection.png

 

The currently selected Point Style and Cursor Style Attributes are highlighted with a blue box, but the Line Style and Line Width are not highlighted with the current values. This is important to know, because it is difficult to tell the difference in line widths, and could even be impossible if the cursor is off the screen.

 

I can only find these two places right now that the current selection is not highlighted, but once I find more I'll post in the comments.

The thumb tack in the palette is handy. But it disappears when we right click a node to find the corresponding palette.

menu2.png

So there has to be extra steps when I want to find more relevant nodes. What I really want is adding the thumb tack to it as in the normal palette, like:

menu3.png

Thank you.

 

Best wishes,

Bo

 

When designing larger user interfaces often times my event structure ends up with many cases sorted in no real order. Commonly there are multiple controls that trigger the same event case. It is cumbersome to try and find the particular event case where a control is handled.

 

Events.PNG

 

What I would like to see is a Find -> Event in the shortcut menu for a control. We can currently search for the front panel control, local variables and property nodes if used. It seems logical that events should be included in that list as well.

 

Right Click.PNG

Currently, if you want to enter in multiple elements in an array, you have to click on the empty element before typing.  It would be more effecient to be able to press tab to enter another element in that array.

I suggest having a feature that would allow us to add "virtual" error terminals to any VI by right-clicking any VI and selecting "Add Virtual Error Terminals...". These virtual terminals would do nothing more than act as pass-through tunnels to facilitate data flow. This would allow us to minimize the use of sequence structures:

 

Example

Many of us would have experienced situation where we would like to have listbox indicator or control as opposed to using array of cluster. For eg.

 

listbox control..PNG

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

This is achieveable with the help of array of clusters containing different control.

 

array_of_cluster.PNG

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

To some extent dropdown menus can be implemented in listbox, but with with large and complex codes with property nodes.

It would be great to have listbox control / indicator which would be simple to use like cluster element; as in below.

buddle_by_name.PNG

Such a listbox element is very useful in product testing application.

In LabVIEW if I want to use a property/method of a control I have to right click and select property. Same for second control I want to use same property I have to do same operation again. My idea is if we select all the controls and right click, some common property like value, visible and etc..... Should display and by selection it generate automatically. This can reduce my application development time.

 

 

Multiple Control Selection.png

 

So if this key feature is there in LabVIEW we can select multiple controls or properties and perform some basic operations to reduce our application development timing.

 

Thanks and Regards
Himanshu Goyal | LabVIEW Engineer- Power System Automation
Values that steer us ahead: Passion | Innovation | Ambition | Diligence | Teamwork
It Only gets BETTER!!!

The useful feature of having an arrow connect a free label to the part of the code it refers to was added in LV 2013. However, there are cases where a label refers to multiple objects, so you would want to point an arrow to each of those objects. Currently this is unavailable. I suggest that this feature gets implemented in following LV releases. It makes block diagram documentation just that bit better.



Attached Labels Now/Future

It would be nice if under options that highlight execution speed for debugging was configurable.  It could also be not an option but placed just next to the light bulb icon.  With experience we become able to folloe the code much faster and having 2 or 3 speeds of highlight execution could save some waiting time.  I know that there are many debugging options already but sometines the old light bulb is easiest.

 

Now that scripting is "legal" we need to be able to do more with it, when it comes to the event structure scripting is weak.

 

Here are a couple of discussions where people wish for more scripting functions around the event structure :

Triggering an event on a picture created with LV Scripting

- Remove Frame Not Implemented

How do I get the cases in an event structure

- Event Structure Selector Labels

 

We need to be able to add and edit event!

I sometimes need to create Front Panels that are to be navigated by keyboard alone, which makes the tabbing order quite important. At this stage, I need to ensure my error cluster controls don't get included in the tabbing order list. Given my error cluster controls for any VI that shows its front panel will be moved out of the visible area, I need to ensure the operator cannot tab to them. Therefore, I would like to see error in clusters have their default "Skip this control when tabbing?" property set to True.

 

I don't think a change to the default property would cause any complications?

 

This idea is a better idea than my previous Error Cluster disabled by default thanks to tst!

Array To Cluster Function, add Type to Convert Cluster

 

I rarely use this function, but when I do I always end up using Variant to Data function for my Cluster Type.

So I would like to add a Type terminal to convert cluster type.

 

111.png


If Type terminal is unwired, this function work as it in current version.

 

If it is wired then it will convert to cluster type, and further it can also be used to define cluster size. So this way we can adjust cluster size dynamically if cluster definition changed.

 

Thanks,

 

222.png

If I'm the first to post this Idea then I'll be shocked.

The Idea is simple. We all love programming in LabVIEW, and I'm sure that we've all at one time or another had a colleague, friend or family member ask if we know how to do something on the PC. The immediate thought is I don't know where to get the software to do that, but I could write a simple LabVIEW app  in a few hours that does the job.

E.G hunt through someone's PC and move all of the jpg files over a certain size to a specific location so they can easily find their holiday snaps.

 

You can't create this simple function for them, because if you do, and build an exe, they still need the Runtime engine.

 

Surely for REALLY simple stuff (File IO, basic comms stuff in the Base LabVIEW edition ...) - not DAQ or anything like that it is possible to create an EXE that INCLUDES the runtime components that it needs and is stand alone.

 

This would open up LabVIEW for the use of making quick gadget like apps for the office as well as test and measurement.

 

I can't se how this could be a bad thing.

If you wanted to use a lot of functions from the same palette, you have to either keep going back through the context sensitive Replace/Create menu or manually search back over to the palette through the Functions palette to get to the functions you need.

 

Wouldn't it be nicer if we could pin that palette down directly from the context menu?

 

Ed.png

 

 

If this has already been implemented in LabVIEW 2012, give this idea a miss!

I inherited lots of VIs with complicated terminal connectors. It is a challenge to determine which terminal is associated with a given control. 

 

Why not highlight the associated terminal when a front panel control has been selected?

 

In other words, currently when I select a terminal, the corresponding control is highlighted. I'm proposing that it should also work the other way -- when I select a control, the corresponding terminal gets highlighted. 

 

I have just figured out a workaround, but it's clumsy. I can temporarily delete the control, observe which terminal goes white, and then immediately restore it with Control Z. But my proposed solution would be cleaner. 

 

Thanks

 

Well as the title says...

 

In the string constant you are able to make a scrollbar visible but this is still inconvenient when only see 2 lines of your whole string when you have a string constant of 50 lines or so... and you 9 out 10 times you don't want to create a bigger field because it messes with your diagram.

 

Therefore a small popup with a only a large textfield would grately simplify things.

 

I came up with this idea when I was writing a error message and there wasn't much space to type the string in, I also had this, http://forums.ni.com/t5/LabVIEW-Idea-Exchange/Need-Edit-Window-for-New-Cluster-Constants/idi-p/12082..., idea in my backhead.

 

What do you guys think?