LabVIEW Idea Exchange

Top Authors

User

Kudos

Post an idea

View All (2)

View All (4)

The Search Results window should contain a “Remove” button. When the button is pressed, the selected item(s) would be "removed and rewired" using the exact same implementation that operates behind the QuickDrop Ctrl + R shortcut. This functionality would be useful when refactoring codebases. Currently the quickest way to remove and rewire n instances of a subVI is to navigate to each instance (perhaps using Search Results Ctrl + G) and perform the QuickDrop Ctrl + R shortcut on each instance. The "Remove" button would enable n instances to be removed in a single bulk operation.

View All (1)

View All (7)

(This is different and less controversional than this related old idea)

Arrays of timestamps only contain legal values and can even be sorted. We can use "search 1D array" to find a matching timestamp just fine.

As with DBLs, there might be a very close array value that is a few LSBs off, but well within the error of the experiment so it is sufficient to find the closest value. We can always test later if that value is close enough for what we need or if "not found" would be a better result.

If we have a sorted input array, the easiest solution is "threshold 1D array" giving us a fractional index of a linearly interpolated value. For some unknown reason, timestamps are not allowed for the inputs, limiting the usefulness of the tool. One possible workaround is to convert to DBLs, with the disadvantage that quite a few bits are dropped (timestamp: 128 bits, DBL: 64bits).

Similarly, "Interpolate 1D array" also does not allow timestamp inputs. In both cases, there is an obvious and unique result that is IMHO in no way confusing or controversial.

IDEA Summary: "Threshold 1D Array" and "Interpolate 1D Array" should work with timestamps.

Allow the user to right-click a given test result on the Results Window called "Retest", which re-runs the selected test, and if the test now passes where it previously failed, it clears it from the Results Window.

Start with this:

Right click on the selection, and select "Retest":

The VI Analyzer just retests the selected tests. And then once complete, it returns to the VI Analyzer Results Window, with the selected tests cleared from the list (assuming they passed):

View All (1)

Change class <-> interface

The request:

The thickness of splitter bars can be resized through the front panel at edit time, but this property is not exposed through property nodes. Why not expose this?

Background:

I use splitter bars all the time for resizable GUIs. They're also cumbersome. Many of the feature improvements I'd love to see have already been captured on this forum. In the mean time, I've got tools for automating what I can -- but I've hit a dead end when it comes to resizing the splitters programmatically. This requested property node doesn't exist and pre-sized splitters can't be copied from template VIs using scripting because the "Move" method throws an error.

LabVIEW for Android systems

View All (3)

LVPROJ : Rename a folder

As the number of classes in a project increases it gets harder and harder to figure out which methods in a class are overridden because you need to scroll up and down to compare the methods listed under each class. A distinctive glyph or icon in the project explorer window would be very helpful. I understand that there are workarounds like creating an override virtual folder and moving the overridden vis inside it or right clicking the class and opening the "VI for Override" window and checking if the vi is listed. However, a distinctive icon would drastically increase code readability.

View All (2)

Empty Variant Function To Variant Palette

Put a copy of the Empty String/Path? on the Variant palette since "this function is also designed to work with variants...; see https://www.ni.com/docs/en-US/bundle/labview/page/glang/empty_string_path.html .

For an example of the difficulty in finding this function, see https://forums.ni.com/t5/forums/editpage/board-id/170/message-id/1248895

For precedent of the same functions on different palettes see the Array to Cluster and Cluster to Array functions on both the array and the cluster palettes.

View All (2)

Replace icon of method overrides

Similar to the library banner functionality, I find myself wanting to replace the icon of method overrides with the icon in the parent. This is done automatically for new overrides, but I haven't seen any way to apply a new parent method icon to its overrides once they exist already.

I imagine this working like the library banner: whenever the VI icon of a dynamic dispatch VI with overrides in memory is changed a dialog could pop up and ask if you want to apply it to the children as if the icon had been freshly generated the way it is for new overrides.

Allow clusters to have "pages"

Have you ever created a cluster like this?

I have. Numerous times. It's fairly easy to create clusters which get out of hand. The magic number is usually around 10-15 elements, assuming some of them are clusters as well, but even if those numbers are manageable, I've also created larger ones, and those aren't manageable.

Using LVOOP mitigates this to some degree, but does not solve it completely.

So, it would be great if we could divide the cluster into "pages" or "categories":

This will allow us to logically divide the cluster into manageable areas.

The names of the pages will appear in the selection list and in the unbundle node, as shown in the example (although you could hide them in the node by unchecking the full names option), but they will NOT actually be part of the element's name. Changing the name of a page or moving an element from page to page will NOT require you to change code which already uses that element.

Notes -

In my mockup I used a tab control. I understand that LV R&D has some aversion to the concept of tabs inside clusters, so I would like to make it clear that I'm NOT asking for a tab inside a cluster. This is purely a cosmetic and organizational feature.
I already posted this as a comment on this idea, but I figured it was worth posting as a separate one.

View All (4)

One of the fiddly things I seem to do more than I'd like is adjust the bottom of block diagram comments to the right height. At a minimum there, but also for similar text boxes on the front panel or subdiagram labels, etc. I'd like to have a snap feature that sizes to a multiple of the text height. Examples:

LabVIEW Idea Exchange

Context Help of Typedef / Custom Control should show the Info of the contained Control

"Find Items With No Callers" needs "Remove From Project" feature

"CTRL + Double Click" on a VI in project windows should open the VI Block Diagram.

The Search Results window should contain a “Remove” button

Automatically create terminal label with In/Out suffix

More array operations should support timestamps (threshold, interpolate, etc)

Add ability to retest one or more selections in the VI Analyzer Results Window

Type conversion to fixed point - should also work for arrays

Delete listbox column/row (header) even when empty

Align terminals between "To More Specific Class" and Property Node

Change class <-> interface

Expose Splitter Bar Width/Height Property through Property Nodes

LabVIEW for Android systems

LVPROJ : Rename a folder

Distinctive icon in project explorer for overridden methods

Consistently expose nested data in Property Nodes

Empty Variant Function To Variant Palette

Replace icon of method overrides

Allow clusters to have "pages"

Snap text boxes to an integer multiple of text height