LabVIEW Idea Exchange

Community Browser
cancel
Showing results for 
Search instead for 
Did you mean: 
Post an idea

LV2010 introduced a new possibility of accessing class private data via property nodes. However, I suggest to reduce the size of the property node when the Name Format is set to Short Names (default). The suffix .lvclass is not necessary.

 

24582iAED03877045EE9C1

Hi all,

 

It will be very convenient to have the ability to change the amount increment in a for loop.  Currently, the i in for loop start at 0 and increment by 1 for each iteration.  It will be great if we can change the start point of i and the amount increment, similiar to what we can do in c.

 

for(i=2; i<10; i=i+3)

 

Yik

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

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.

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

A LabVIEW application installer generated from App Builder creates multiple folders and files in the folders. It is desirable to have a single file installer so that customers see only 1 file to install.

Have you ever wanted to place a probe on a loop iteration counter? I can't tell you how many VIs I have with a wire from the iteration counter to the loop boundary just so I can put a probe there (Maybe a pop up iter. count would suffice). Or probe an output terminal on a VI that is not wired. I know you can open the VI and put a probe on the wire but..

 

There are probably more cases.

 

Minor issue, but since we have a chance to ask..has been bugging me for about 20 years now.

 

 

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

 

Add a new button to the search results dialog called "Set Aside" so I can have multiple search results open at the same time.  Put it near the bottom just below the search results.  When you click it, it changes the title of the window to "Search Results - Set Aside 1".  If you click "Set Aside" again when #1 is open, it will open "Search Results - Set Aside 2" ... and so on.  This way you can have several different search results open simultaneously.  I love the check mark feature in the search results, but it resets every time the search windows is closed or overwritten by a new search.  Thus I lose my place if I want to make sure to check every instance of something but need to search again while looking at one item.

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!!!

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

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.

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

 

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

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!

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

Currently, digital displays are free floating and are not the same height as their corresponding plot in the legend.

 

before.PNG

 

Also, when an additional plot is added the displays no longer line up.

 

added.PNG

 

I would suggest including the digital displays inside the Plot Legend.

 

embedded.png

 

It could be a property of the graph so the user could choose to turn the option on or off

 

properties.PNG

 

Note: The current method to have a similar effect is to lock the entire chart so that it cannot be edited (KB 4VQDROPI)

When creating complex UIs with a lot of controls on the front panel, it is difficult to find the control we're trying to associate an event with from the Edit Events dialog, as controls are not sorted alphabetically. It seems they are sorted in the order we create them. Sorting them alphabetically would improve our efficiency as it takes more and more time to find the control as rthe UI grows.

 

Edit Events Dialog

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 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!