LabVIEW Idea Exchange

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

It would be nice if there was some option to configure the separator behavior of combo boxes. Currently, entering a hyphen (-) as an item turns into a separator automatically, and there is no way to configure that. What I think would be best in terms of configuration options is a "Separator Value" property in the Edit Items tab of the Properties dialog. The hyphen could be the default value, and it could be changed to an alternate character or character sequence if the developer needs the hyphen to appear as just that for whatever reason. If the value of the property is empty, there are simply no separator lines created.

 

FireFistRedhawk_0-1779113435039.png

 

There is also a bug involving the hyphen as the separator value. When a combo box has the Allow Undefined Strings property unchecked and also has a separator as one of the items, a hyphen is still treated as a valid entry since it is technically one of the values present. This bug exists in the most up-to-date version of 2026 at time of writing, 26.1.2f2. I think the existence of this bug warrants taking a look at the separator behavior in general, but also possibly adding this idea as an enhancement to it.

Having consistent (and therefore predictable) right-click menus is essential for maximizing coding efficiency.

 

Most structures have the following right-click menu items:

 

Visible Items
Help
Examples
Description and Tip...
---------------------------
Add Breakpoint
---------------------------
Structures Palette
Auto Grow
Exclude from Diagram Cleanup
<specific menu 1>

<specific menu N>
Replace with <other structure type 1>

Replace with <other structure type N>
Remove <structure type>
---------------------------
<other specific menus>

 

The right-click menu however has some inconsistencies regarding item order and menu separators for certain structure types:

 

1. "In Place Element Structure" has "Replace" and "Remove" items reversed:

raphschru_0-1778671181846.png

The "Remove" item should always be the last one in the item group (right before the separator) since it is a very common action and the separator offers a quick visual reference point.

 

2. Depending on whether you click on the structure border, the frame name label or the subdiagram label, sometimes an extra item separator appears for no reason:

raphschru_3-1778673447637.png  raphschru_6-1778673672106.png  raphschru_5-1778673565395.png

 

The grouping of the generic items shouldn't vary depending on where you click on the structure. Here we sometimes have 4 item groups instead of 3, which hinders quick menu identification and selection.

 

3. This is more a general remark, but I think items specific to a structure type shouldn't be mixed with the generic ones in the first 3 groups (except maybe for the "Replace" items, since they are related to the "Remove" action).

 

So any specific menu item should belong after the first 3 groups:

raphschru_2-1778672934373.png  raphschru_7-1778673846675.png

raphschru_8-1778673934000.png  raphschru_9-1778673982744.png

 

This last remark could be subject to discussion though, as configuring iteration parallelism and shared clone allocation could be considered a "primary" action (therefore requiring to be closest to the top), even if it is specific to certain structure types.

 

Regards,

Raphaël.

Windows Clipboard History is a very useful tool in Windows to manage copied data. But it doesn't work with LabVIEW content. Right now, when pasting copied VI content from the clipboard history, it is pasted as a regular image.

 

I am not sure how copy paste VI content works under the hood, but since VI snippets are regular png images, I guess this should be feasible. 

 

Not too long ago i learned of the excellent Quickdrop command "Remove Unconnected" (ctrl+shift+r) on Build array and (un)bundle.

However it doesn't work with Index array and i wish it did. 🙂

That's all!

Yamaeda_0-1777370033284.png

Ctrl+space -> ctrl+shift+r ->

Yamaeda_1-1777370073167.png

 

Suggestion, it should work in this case also!

Yamaeda_2-1777370165875.png

 

Quiztus2_0-1777992326142.png


The layering of values shown during highlight execution mode should take the data type into account. I suggest moving types whose values do not change—such as refnum or lvclass—to the back of the display stack. This should also apply to ordinary VIs, similar to how property nodes are already handled. Otherwise values worth to know are hidden by actually useless info.

Add a context menu option to open class private data directly from block diagram / panel.   Currently need to select "Show Class Library" then expand and open control from Project Explorer.   During initial development I'm needing to modify private data frequently and this is how I'd expect to do so based on Typedef behavior (right click - Open Typedef)

 

class private data.png

Currently converting a string to an array loses the "Size To Text" property, this should be preserved to maintain the desired display after conversion

change to array size to text.png

When creating a Polymorphic VI, please let us add VIs more easily.

 

Intaris_2-1776154590598.png

 


Either allow multi-selection of VIs when choosing "Add" (Button in Red) or allow drag and drop of multiple VIs from a project or explorer (Blue area is a target for drag and drop).

 

While I'm at it, please allow selecting and editing the "Menu Name" and "Selector Name" in place. Having to go through a button press and a dialog for each and every VI is tedious.

Customer received this error after trying to send J1939 frames on XNET Bus Monitor,  once user select J1939 database , there is no option to transmit frames ,  not sure why XNET Bus monitor does not have that tab,  xnet does it support it, using a labview code is possible but xnet bus monitor is something very practical for Customer to use before going to code.

Also when this type of error occurs need to have better description as J1939 and CAN FD not supported in XNET Bus Monitor.

drag.gif

Dragging block diagram objects across structure boundaries preserves wiring correctly when tunnels are involved, but it fails when shift registers are used. It should be feasible to adjust this.

1.png

 

 

 

 

 

 

 

 

 

 

 

 

2.png

 

Idea: The "Text Color" and "Background Color" fields of LVTextColorsTypeDef.ctl should be replaced with a Color Box

 

This suggestion is very similar to the following idea, which was kindly implemented in LabVIEW 2025 Q1: The "Color" field of LvFontTypeDef.ctl should be replaced with a Color Box

In large-scale LabVIEW projects, performing a text search across the entire project hierarchy can take a significant amount of time to complete, especially when the codebase contains numerous VIs, libraries, and dependencies. Currently, the search results can be browsed(doble click and locate the search result in the code) only after the entire search operation has finished.

It would be highly beneficial if the search results could be browsed incrementally while the search is still in progress. In many practical cases, the desired result appears early in the search process. Allowing users to review and navigate through the partial results as they are discovered would enable them to quickly locate the needed item without waiting for the full search to complete. If the relevant result is found early, the user could simply stop the search operation, thereby saving valuable time and improving overall productivity when working with large LabVIEW codebases.

 

Sample.png

 

Please add your opinion.

 

Regards,

Adarsha Pakala

LabVIEW from 2006

CLA From 2014 

 

The default cursor color in the Fuse palette is yellow, which is nearly impossible to see:

 

cursorcolor.png

 

Since we can't set a default cursor color for a graph, and there are no events exposed that let us know when the user creates one, can we at least get the default color to be somewhat visible? Maybe dark gray?

Occasionally, we want to defer panel updates and most often it is just the current front panel. Unfortunately, the defer property node absolutely requires a wired reference to the panel.

altenbach_2-1770235627004.png

 

 

 

In the past it always took me quite a while with many dead ends to get it right. For example, one might try to do the obvious and "right-click...link to..Panel", but that does not work! I challenge anyone to get that panel reference in under 60 seconds starting with a generic property node from the palette. Just try! (Hint. After selecting the right class (VI Server...VI...VI), the drop down lists it as "Front Panel" and not "Panel".)

 

The idea would be to allow defer nodes without a wired panel reference and they would just act on the current front panel and not break the VI.

 

Note that the panel reference defaults to the current VI and does not require a reference, so why can't the defer node do the same?

 

(Note that we also have this old idea, which would simplify things...)

 

The Class Browser (Ctrl-Shift-B) is a little-known LabVIEW feature that makes it much easier to work with property-based class hierarchies in LabVIEW (VI Server, DAQmx, VISA, Sys Config, your own .lvclasses, etc.). The Class Browser search function is particularly helpful when you aren't exactly sure what property or method you need, or if it even exists. Unfortunately, the search results are often very difficult to navigate, as in this example:

Darren_0-1767913475591.png


I was looking for a property or method relating to locking controls on the front panel, so I searched for "lock". Over 1000 results were returned. But the results include a tremendous number of duplicates. If there is a property of a parent class (like the Is On Block Diagram? property of the Generic class in the screenshot above), then that property will be duplicated for all child classes of that parent class... in this case, there are hundreds of children of the Generic class! It took me a few minutes just to scroll through all these duplicate results to finally find what I was looking for (the "Lock Objects" method of the Pane class).

Idea: Only show the parent class property/method in the search results of the Class Browser window. Do not show child class entries for that same property/method.

In the example above, if duplicates had been removed, then my "lock" search would have returned 49 results, which is a much more reasonably sized list of results to dig through.

Replacing a cluster constant should not alter its 'View Cluster As Icon' setting.

 

Combined Image.png

 

The bug manifests itself regardless of the method used to replace the constant: via QuickDrop Ctrl + P tool or via right-click >> Replace menu.

When working with classes and interfaces, I often use the right-click option on classes to navigate to their parent class.  I regularly find myself trying to do this with classes that inherit from interfaces too, but...this isn't made easy.  It'd be nice if there was a right-click menu option on classes to navigate to their parent interface(s):

 

Untitled.jpg

The interpolate 1D array function has a powerful but under appreciated feature of being able to do segmented linear interpolation when the array input is an array of points.  (For example in an array of PID profile setpoints).  The interpolate function will directly produce the correct interpolated y value for any 'segment' in the array which is very cool.  However it does not expose the threshold index which would be very useful and is most certainly already computed internally.  In the use case of traversing an array of PID profile setpoints, it would be good to know what segment is being interpolated at any given time.

The Rearrange Cases window (which appears when clicking the Rearrange Cases... menu item on Case Structures and Event Structures) would benefit from having "Move Up" and "Move Down" buttons, just like the "Edit Enum Items..." window.

 

Rearranging cases currently requires dragging and dropping. Using Move Up/Move Down buttons can be more precise and easier on the hand.

 

1 (edited).png

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

2.png

Add a note here if the VI is dynamic dispatch to aid in code readability:

avogadro5_0-1776205743247.png