LabVIEW Idea Exchange

Top Authors

User

Kudos

Post an idea

View All (1)

Unique Icon for LVDateTimeRec.ctl

View All (1)

When programming with large applications, often times you'll have clusters carrying a lot of information. If you hover over the cluster wire and observe Context Help, you might see something like this:

This Context Help window above is rather large and doesn't necessarily make it any easier to see the structure or contents of the cluster. My proposed idea calls for the ability to expand or collapse the cluster contents within the Context Help window, such as this:

What do you think?

View All (2)

NI's response to the ideas thus far appears far too sporadic. For example if you check out the top LabVIEW ideas (http://forums.ni.com/t5/ideas/v2/ideaexchangepage/blog-id/labviewideas/tab/most-kudoed) 7 of the top 10 ideas are still listed as new! Adding insult to injury the average age of these ideas to date is 1,017 days! It is ok to decline ideas but please provide us some indication that this is something you take seriously. It would appear that NI is cherry picking the easiest half dozen or so items from the list so you have a marketing gimmick to list on the LabVIEW release notes. I propose that a threshold is set and made public so that if an idea reaches a certain amount of kudos, R&D must address it, even if that means declining it.

View All (5)

Quick Drop Replace Terminal

View All (1)

(note: this idea is similar to this one, but different enough that I thought it warranted a new post)

LabVIEW 2019 will include a Clean Up Front Panel feature that repositions front panel objects to match their positions on the (already wired) connector pane. I think we should also consider implementing the opposite behavior, where you can arrange your front panel the way you want your connector pane, then assign that arrangement to the (currently empty) connector pane:

I envision the gesture used to employ this feature would be a Quick Drop Keyboard Shortcut, an entry in one of the drop-down menus, or a right-click on the Connector Pane.

In LabVIEW you need to know the number of sub matches at edit time and cannot handle arbitrary regular expressions. It would be nice if there was a regex function that returned sub matches in an array which can be handled much more abstractly than a pre-sized xnode.

C++, the regex utilities return a container-like class https://www.cplusplus.com/reference/regex/match_results/

PHP an array of matches is returned https://www.php.net/manual/en/function.preg-match.php

JavaScript returns an array of matches https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/String/match

View All (4)

Hello,

I'm telling my strudents how they should use the error cluster and how important it is. In subvis no error dialogs should be shown and so on (see topics of LabVIEW Core 1 / Core 2).

But many VIs written by NI have been programmed very sloppy.

Example: VI "Write into spreadsheet file". The error cluster is not wired to the inputs/outputs and if an error occures, an error dialog would pop up. Here is the block diagram of your V "Write into spreadsheet file"I:

Please check all of your VIs and do a revision that we can make well-coded applications where the error handling will work correctly.

Regards

View All (3)

View All (4)

Let's say I have a ring control filled with lots of of items, but I decide that it would be better for the user if he could see all the options without having to pull down the ring. I right-click on the ring control, choose replace and select a Listbox. Now I have an empty listbox though, and I have to recreate the list. Most of the times when I do this I want the items I had in the ring control to transfer to the new control, like this:

replace with content carried over.png

The transfer of items should work both ways, and apply to similar replacements, like a change from ring to enum e.g.

It would be nice to have a way to choose whether to keep the items or not of course (key control while doing the replacement or a dialog asking if you want to keep the items), instead of having to delete the items afterwards if you did not want them, but I am not sure it would be needed that often. I would be perfectly happy for the default to just keep the items.

PS. Writing a quick drop shortcut plugin is one existing way of getting this functionality without having to wait for NI to implement it in the IDE...Perhaps someone has already done that (?). This request is for it to become (or be a part of) the default behavior though.

Easier Reordering of Terminals

This is a follow on to this idea. After terminals are wired to growable nodes. Make it easier to move and reorder the terminals. The switcharoo tool exists if there are only two terminals but it is difficult if there are more.

I suggest making it easier with a keyboard/mouse combination or mouse long hold or something like that, to select a terminal. Then let the user drag it to another terminal and drop it. If that terminal is wired swap the selected wire and the one dropped over. If not wired, move the wire connection to the terminal dropped over.

View All (2)

Filter/Search for Parent Class Selection

On bigger projects, when creating a new class, I find it time-consuming to track down the parent class I'd like to inherit from.

It'd save me some pain if there was some kind of filter and/or search option for this on the New Class GUI:

Other thoughts on this:

- While the tree structure is useful, I usually know the name of the parent class I want to inherit from, but I don't necessarily know the full inheritance of it, meaning the tree structure isn't the most efficient way to find it. (Even alphabetical by class name would be faster in these cases).

- I'd find the tree structure here easier to follow if the lines were visible.

View All (1)

While writing/debugging applications that make heavy use of reentrancy it is not uncommon for a reentrant VI to be left open after the rest of the application has shut down. This leaves VIs, Classes, LVLIBs locked in the project and your only recourse is to hunt down the offending reentrant item or close the project and reopen it.

It would be valuable to be able to see the running clones in the list of reentrant items found by navigating to View>>Browse Relationships>>Reentrant Items, maybe denoted by a *, like this below:

Having that would easily allow me to open the running clones and close them out manually so I can continue debugging.

View All (2)

View All (5)

Align input and output of Select function

View All (2)

LabVIEW could use a feature that's commonly used in C++, the "final" specifier for a class override method. This would allow a child class to override a method from a parent class (or interface) and then prevent child classes of itself from overriding. Currently, with large inheritance structures, it becomes difficult for developers to create child classes since so many of the methods can be inherited from. The final specifier would allow you to create intermediate classes that define certain override functionality that does not need to be further overwritten and only pass on the ability to override methods that are important to child classes.

FInal Override.png

View All (5)

LabVIEW Idea Exchange

Webservice Swagger/OpenAPI document generation

Unique Icon for LVDateTimeRec.ctl

Expandable/Collapsible Clusters in Context Help

Require LabVIEW R&D response to any idea over N kudos

Quick Drop Replace Terminal

Make Connector Pane Match Front Panel Arrangement

String control/indicator/constant with code formatter

Provide regex functions with match outputs as an array

Revision of many VIs written by NI (usage of the error cluster)

Provide a malleable "Traverse For G Objects" function

LabVIEW Find Search Scope - Add user.lib

Keep items when replacing ring (or enum) with listbox (and vice versa)

Easier Reordering of Terminals

Filter/Search for Parent Class Selection

Numerical Data Type Color Representation on selection pallette

Show running clones while browsing relationships>Reentrant Items

Add licensing and activation tools for packed project libraries (PPLs)

Align input and output of Select function

Allow for "Final" specifier on Class Override

quick-activate-button for disable-structures