LabVIEW Idea Exchange

Top Authors

User

Kudos

Post an idea

View All (7)

Search in VIs of last search

I would like to be able to search in the VIs which were in the previous search results.

Currently this is not possible. When I do a search in a VI I can select to search in three different scopes:

all VIs in Application Instance
Selected VIs
current VI

I see two possibilities for implementing this:

as an additional search scope (like "VIs of the previous search result")
as a button in the dialog "Select VIs to Search" (poping up when clicking "Select..."), labeled "Add VIs of previous search result"

The second option has the advantage that it is clear defined what happens with the selected VIs when repeating a search.

View All (3)

For large projects with multiple developers, it will sometimes be necessary for more then one developer to modify the project file. It would be helpful to rapidly identify these changes by comparing working copies with copies from source control.

In the attached picture, you can see how a red circle highlights the difference between two project files.

View All (1)

When I want to insert a VI into a wire, I often have to navigate a long way in the palette until I reach the VI I want to use. The same is true when I replace a VI. Both palettes have a special top level with direct access to palettes LabVIEW thinks I might use. But this is often different from what I want. This is why I ask for including the favorite palette menu in this special top level menu. Then I can keep a short navigation to whatever I want to. (Of course it is only one level shorter tahn before, but the entry point to favorites is much more prominent.)

View All (5)

I'm shocked that this doesn't exist, but via help ticket verified that there is no way to do this (or they couldn't figure it out at least).

The following snippet shows what seems like would be close, but they are actually referencing VI's (none of these work):

What I'm after is figuring out the entire heirarchy above the current class level. I solved this by making a method that passes out it's name and forcing overridden methods below the class. This works well, but I'm annoyed that I have to create code for what is obviously available somewhere in memory already.

View All (2)

In a standardized architecture, there are some cluster that need to be specfic to the current project.

In labview 2013 the reference to these clusters was automatically done without preserving default value.

In newer version of labview we have to review and update each specific cluster contained in the common part of the code .

It would be great to make an exception on some type def, on which the default value doesn't really matter.

Currently, if the user edits the X or Y position of a cursor, this doesn't fire any event (that I am aware of), while in effect is is equivalent to the user grabbing the cursor and instantaneously moving it to a new location.

There is a "Cursor Move", "Cursor Release" and a "Cursor Grab" event, as well as possibility to catch the user selection of a cursor contextual menu event such as "Bring to Center".

It is possible to check whether the user

My suggestion: Add a "Cursor Location Edited" event for Graphs with cursors

View All (1)

Please vote to improve the help. NI wants votes before improving the Desktop Execution Trace Toolkit help! The various log events should be defined. Service request reference#7718574 said:

"It seems that the information regarding the descriptions of the Desktop Execution Trace Toolkit Events is not publicly available at this time" and that it could be requested via the Idea Exchange here.

There are about nine event types which have a short description (Errors, Event Structures, Memory Allocations, Queues and Notifiers, Reference Leaks, User Events, User-Defined Trace Events, VI Execution, VIs). There are several events under each category which are not described. Some are not self-explanatory. For example, what is the difference between the VI Execution's Call and Start Execution or Return and Stop Execution? (rhetorical)

View All (1)

Build Specification Version Information

In the Build Specifications under Version Information one has the option of setting the Version Number of the build. Ther Version Number is of the form Major.Minor.Fix.Build.

There is an option to Auto Increment the Version Number. If this is selected the Build component of the Version Number is automatically incremented every time the specification is built.

I always use this setting since I can thereby tell the difference between builds. The major annoyance here is that although only the Build component is automatically updated all four controls are disabled and grayed when Auto Increment is selected. That means that every time I want to change the Major, Minor, or Fix part of the Version Number I have to uncheck Auto Increment, make my changes, and then re-check Auto Increment. More than once I have forgotton to re-check Auto Increment, which then screws up my numbering scheme.

Idea: When Auto Increment is selected for the Version Number, only disable and gray out the Build control. Leave the Major, Minor, and Fix controls enabled.

From:

https://forums.ni.com/t5/LabVIEW/possible-to-change-opc-ua-alarm-limits-at-runtime/m-p/3688481

The request is mostly in the title. Right now it seems as though changing an alarm limit requires stopping the OPC UA server. It seems reasonable to expect that users may wish to adjust alarm limits on the fly -- for my use case, tuning the system during a long commissioning process. It might be many months before a system is fully ready to go, and during that time alarm limits change regularly and we still want to report alarms to operators during this period.

If a class is contained in the private data cluster of another class, this is the LVOOP equivalent to an Association (as OOP concept). I'd like to optionally display this relationship of classes in the Class Hierarchy window. It should also work for nested structures (class in array, cluster, DVR).

As used from normal BD programming, different kinds of wire should be used to identify details of the relationship:

green color if it's a by-ref relationship (DVR, SEQ);
double wire if it's contained in an array;
an directional arrow symbol would be necessary to indicate the navigable end.

The following would be nice to have, but partially difficult to implement:
In addition there should be a way to annotated the associations to indicate when the intended use is restricted to a child class, such as class that contains objects of the type of the same class. Here the association would point to an ancestor of this class. Either we should be able to put a comment on the 'wire' to document this intention. Ideally we could be able to wire classes with recursive associations (which are not possible in LVOOP, hence this should also not have any effect on the code by only be documentation), and link it to the implemented association wire.

View All (3)

"Undefined" as a new value

Double variables can have the non-numerical values NaN, +Inf and -Inf. I would also like to be able to give them the value Undefined, and that applies to all kinds of variables (integer, boolean, string, etc.). This could solve issues that other users have posted:

- To make a test for inputs of subVIs if they are wired or not. Give them Undefined as the default value.

- A ternary boolean.

- If you want to force the user to fill inn data in the main program, there must a way to see if data has been entered and not a default value. This can be done by setting Undefined as the default value.

How to handle the Undefined value:

Any operation on an Undefined value should give Undefined as a result. The only exceptions are two test blocks [Is Undefined] and [Is Defined].

This can also be useful for debugging in a tangled block diagram to see if input A really has a connection to output B. If it is, then B should be Undefined if A is set to Undefined.

View All (2)

Add LV version to window title

When I am running multiple version of LV at the same time I have a hard time telling by sight which version a given VI belongs to. As others have noted, double-clicking opens the last version used, regardless of the VI version. This leads to occasional upconversion when an 8.6 VI is opened in LV2009 and subsequently saved. Every time I want to create a new VI I have to double-check which version I have open using 'About LabVIEW' or checking for subtle differences in the pallettes. I would appreciate it if the version appeared in the title bar of the window. In fact, any visual cue would be helpful.

View All (2)

The tendency of LabVIEW to indicate that 5 or 10 VIs have been changed for every VI actually edited makes maintiaining organized, legible version control logs difficult. To be kind to my co-developers, whenever possible, I try to keep the number of spuriously modified VIs down by intentionally not saving VIs that do not need to be saved. This would be a lot easier if the "Save all (this Project/Library/Class)" menu item behaved as it sounds intuitively. Currently, it functions to save all of the items in the Project/Library/Class, as well as their dependencies. In 99.9% of all cases, I did not intend to modify any dependencies. If I had intended to work on them, they would be in the library or project.

This idea is to have the "Save all (this Project/Library/Class)" menu item save only items inside the Project/Library/Class, and not their dependencies.

LabVIEW Idea Exchange

Monitor Input for File Dialog Function

Search in VIs of last search

Perform Diff and Merge on project files

Include the Favorites Palette in the menu "insert into" and "replace"

Add property to a class to get parent and children classes in the inheritance hierarchy

Review and Update from Type Def. should have exception to auto-validate the changes.

Create a "Cursor Location Edited" Event for Graphs with cursors

Add browsing the VI's owning project/class/lvlib in the functions/controls palette

Front Panel property that returns a .NET IWin32Window handle

Reorder Multiple Plots by Dragging Order

Add DynamoDB support to the NI cloud toolkit for AWS

Keep Quick Drop window open with last selection

Desktop Execution Trace Toolkit Help for Events

Build Specification Version Information

allow editing of opc ua alarm limits without restarting the server

Graphically display 'Associations' in the Class Hierarchy

"Undefined" as a new value

probe watch window scroll position memory

Add LV version to window title

Do not save dependencies when using "Save all (this Project/Library/Class)"