From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.

We appreciate your patience as we improve our online experience.

LabVIEW Idea Exchange

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

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

It would be useful if a special free label existed on the block diagram and/or front panel whose contents would be kept in sync with the contents of the VI description. For brevity, let's call this a Description-Linked or DL label. The screenshots below show an example.

 

1. The DL label shown on the block diagram

DL label 2.png

 

2. The DL label shown on the front panel.

DL label 1.png

 

3. The DL label shown in Context Help

DL label 3.png

 

4. A possible mechanism to show the DL label on the BD and/or the FP

DL label 4-edited.png

 

Suggestions

  • The DL label should have a distinctive background colour that cannot be changed (could be any pale colour)
  • It should be possible to show the DL label on both the BD and FP, only on the BD, only on the FP or neither in the BD nor the FP
  • Screenshot 4 shows a possible mechanism to show/hide the DL. There may be better mechanisms out there.
  • Selecting a DL label on the BD or FP and pressing DELETE (like when deleting a regular label) hides the DL label on the BD or FP respectively. Equivalent to unchecking one of the checkboxes in screenshot 4.
  • The two settings for showing/not showing the DL on the BD and FP should be stored within the VI. The settings should be preserved when creating a 'Save as...' copy of the VI.
  • It should be possible to independently resize and move the DL free label instance on the BD and/or FP (the size and position of the rectangle is not synced). Notice the size of the rectangle isn't the same in screenshots 1 and 2.
  • The DL label has no influence on whether other free labels exist in the BD or FP. Any number of free labels are still allowed.

This idea would ease the process of creating and maintaining well-documented code

  • When using a subVI inside a caller VI, the Context Help documentation is extremely useful (it may be the only documentation available if the subVI is part of a PPL)
  • When editing or inspecting a VI, the Context Help documentation is often not at hand. What is available at a glance is often a big free label comment somewhere on the BD or FP
  • As the VI is edited, the big comments on the BD and/or FP inevitably become out of sync with each other and with the Context Help
  • The DL label introduces the concept of having a 'master' documentation source, or a single source of truth
  • At Renishaw UK, some of us use an in-house scripting tool that searches for a free label containing the first word 'Description' on the front panel, and copies the remainder of the text into the VI Description. It's a useful workaround, but this idea would remove the need for such workarounds, and would add the benefit of two-way syncing (editing the VI Description to update the comments in the BD/FP).
  • drjdpowell suggested a similar idea (but not identical) in a comment to idea Subdiagram label for Block Diagrams too (screenshot below).

 

DL label 5.png

 

Thanks!

Right now we can point the comment to only one section of the code or one function.

 

It would be more effective sometimes, if we could point the comment to multiple sections of the code or multiple functions.

 

 

 

AdarshaPakala_0-1649056793758.png

 

 

AdarshaPakala_1-1649056830660.png

 

AdarshaPakala_2-1649056845658.png

 

Than you

Adarsh

LabVIEW from 2006

CLA from 2014

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

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

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)

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

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!

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

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!

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

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

 

The idea is to know the result of the tunnel mode condition, in this case, it is to know if any element has been indexed.

 

whileconditional.png

 

This publication is motivated from the following discussion: Tunnel Mode Conditional .... output condition (by @ouadji)

 

Regards.

Hi,

 

I suggest that radix is always visible when the numeric display format is other than decimal. Is this number decimal for instance?:

 

Number_188.png

 

Well, it was hex:

 

Number_x188.png  ... -> ...  Number_392.png

 

Basically you'd know that if there isn't a radix visible, then the number is decimal. It should still be possible to show radix for decimal numbers as well. This should be the case for both constants and controls/indicators.

 

Just one of those little things that would enforce a minimum of documentation.

 

Cheers,

Steen

 

 

The issue is that there are some situation where we have multiple developers using the same PC (Ex. limited number of test stations where HW/SW integration is performed).  The last developer on the station changes the Environment Options to their desired settings.  

 

To allow a developer to quickly switch to their preferred set of Environment Options, we would like a feature that would allow the following from the LabVIEW Splash Screen: (see image suggestion below)

 

  1. Save current Environmental Option settings and assign that set a name.
  2. Export/Import to from system using a file.
  3. List the Environment Option sets currently on the system in the Tools menu
  4. Recall Environment Option set by name

 

Tools Menu.jpg

Just a simple idea to add an item to the RCM to 'Clear Data' or 'Reset to Not Executed'. It would be handy when troubleshooting to know the values are from 'this' execution.

McQuillan_0-1644407669366.png

 

It would be nice if the conditional tunnel would be polymorphic.  They only accept Boolean as condition.  Please add the error cluster, like it is available on Case Structure.

PolymorphConditionalTunnel.png

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