LabVIEW Idea Exchange

Top Authors

User

Kudos

Post an idea

NI send us the NI Developer Suite each year on DVDs all packed in a nice little NI branded dvd carry case. We are on the SSP suscription and we receive 3/years, which means I have a whole stack of them.

I suggest that NI start shipping USB keys instead. USB has several advantages:

USBs are smaller
USBs are more usable on devices without DVD player
Installing with one large USB means no more DVD swapping. I can go to lunch while NI installs/updates without having to change the DVD every couple of minutes.
USBs are reusable: when you get a new version on LabVIEW on a new USB, you can use the old one for regular usage. This also means less waste, since the USB keys are still in use after a new version ships, but the DVDs are useless.

According to my understanding and the following discussion:

http://forums.ni.com/t5/LabVIEW/Why-exactly-can-t-I-inline-this/td-p/3126562

certain types of Property nodes and Invoke nodes should be inlineable without any great problems.

I would suggest that the LabVIEW compiler get's a bit smarter about this aspect of limiting the ability to inline code. If there's no technical limitation regarding inlining of a property node or Invoke node which is fed with a reference (which does not originate from a local object i.e. a static reference to a FP object) then it should be inlineable.

View All (9)

This is minor one but it bugs me every time.

I create a new control and forget to change the type from "Control" to "Type Def.".

If I'm lucky I spot it after I drop it for the first time on the BD but sometimes I have to replace quite a few instances after I spot the error.

While there might be usecases for a custom control without it being a type def I think that most users want to use type defs when using custom controls.

Therefore please make the default type of new controls "Type Def."

While replacing the Property nodes with Invoke node, Call by Reference, Start Asynchronous call and Wait on Asynchronus call, the primitives are shifting the origin disturbing the wires. So a cleanup is reaquired all the time whenever the items are replaced. It would be very helpful and infact time saving if this is corrected.

Place a Property Node in BD with the Error in and Out connected

Replace the Porperty Node with an Invoke Node

Repeat the same with other primitives

The same behaviour is not found when the Call by Reference, Start Asynchronous call and Wait on Asynchronus call primitives are replaced with one another.

View All (1)

In many cases where I use file path constant instead of control. For selecting a path either we can right click and select browse for path or paste a copied path into the constant.

So it would be a nice and handy option to have a browse button along with the constant as the control has. This button won't respond when the code is executing or while the BD is in run mode similar to the other Enum/Ring constants. This button can be enabled or disabled or made always to be enabled or whatever may be the best approach. This button may be disabled when "invalid path" is selected.

Mockup 1:

Mockup 2:

I have modified the Path constant suggestion and now I feel its not going to take more space.

Suggested style:

Mouse turns to select pointed when hovering over the button.

Upon clicking the button the browse window appears

Hi,

There are numerous ideas floating around about where the color box constant and control should be located in the palettes. How about if there wasn't a distinction between a color box and its numeric representation? Like the "View As Icon" option on terminals and clusters, I suggest a "View As Color Box" on numeric constants and controls/indicators:

I'm undecided on if this options should be available for all numeric data types, integers only, or U32 only, and what should happen to the Representation options when the numeric is a color box. I see at least these options (ordered after my preference - I prefer 1) the most):

1) The "View As Color Box" option is available for all numeric data types, but when selected the data type changes into U32. If you change Representation to anything else but U32, the "View As Color Box" option is automatically deselected.

2) The "View As Color Box" option is available only when the numeric is U32.

3) The "View As Color Box" option is available for all numeric data types, and coercion happens between the selected "color value" (U32) and the true Representation of the numeric.

Several ideas would be fixed by this, for instance this and this.

Cheers,

Steen

View All (1)

Unbundle By Name ( Wiring )

View All (1)

View All (3)

If you have open the Bookmark Manager and
you change one bookmark, the Manager gets an "Bookmark Info Change" event and reloads all bookmarks from all
VIs in the project. The event that triggers the update is the
application event "Bookmark Info Change". At this event there is no
info in which vis a bookmark has changed. If the event would provide the info which VIs have changed,
the Bookmark Manager would be able to reload only the bookmarks from this particular vis.
On larger projects the Bookmark Manager needs minutes (Time and CPU
load) to update the whole list. The additional event data node can be an array of vi names or references.

This changes will fixed also the EventQ Problem of the Bookmark Manager. If the Bookmark Manager is open and you change several Bookmarks the manager reloads all VIs for x times because everey change generates a "Bookmakrs Info Change" Event.

View All (3)

I recently noticed that some of my fitting model VIs were excessively large on disk. It turns out that during debugging long ago I made the current values the default so I can run it standalone. This also meant that the data variant control contained a gigantic kernel matrix.

For some reason it is not obvious how to clear the variant (in order to be able to make the new value default and make the VI small again).

For example for the nonlinear fitting model templates, the data is not shown by default, obscuring the fact that it is the culprit for the excessive size. This also makes clearing the variant tedious (right-click...show data...select all data...delete...right-click...uncheck show data...).

IDEA: I propose a new menu entry: "Right-click...data operations...Clear Data" or similar.

See picture. Thanks!

Create cluster out of selection

View All (4)

It would open a copy of the project that has been copied to a user selected directory along with all its dependencies.

The same thing can be accomplished by immediately doing a Save As>>Duplicate .lvproj>Include All Dependencies. But I have on several occasions "checked something really quick" only to come back to a modified example I didn't realize I modified.

In addition to making this very common copy operation simpler, it would be a nod to new labview users that they need to create copies of examples before modifying them.

On downloading a file from internet and if the file already exists (file with the same name), it automatically appends an auto-incrementing number to the file name, wouldn't be it nice to have the similar feature (may be optional) with Open/Create/Replace File Function.

Consider the scenario, you've enabled this option ('append number if file already exists' as shown in above figure) while using Open/Create/Replace File Function and operation input is 'create' and name of the file is MyFile.txt, which already exists then this fuction should create a new file with name MyFile (1).txt (or may be MyFile (2).txt if MyFile (1).txt also exists and so on).

Hi All,

there is a visual preview of context of hash tags in bookmark manager available for download form ni.com.

This tool allows for quick understanding what is the code around the has tag which help to easily understand if this is the hash tag that I need.

This is the visual bookmark manager: https://decibel.ni.com/content/docs/DOC-31854

Lets add the same option for "Choose Implementation" dialog for OOP in LabVIEW, so here:

I would do this myself but the "Choose Implementation" dialog is pass protected.

Thanks, Piotr

View All (4)

Make the Error Ring Searchable

I'd like to suggest that the error ring dialog ("Select Error") have an entry for a search expression.

For instance, I'm looking for an error code for an index out of range. I might enter, "index" or "range" as the search term, and browse the resulting error codes whose descriptions include that text.

While I don't find myself using the error ring itself very often, I do use the resulting dialog quite a bit to browse for appropriate error codes. The trouble is that there are a lot of error codes and you could be staring at them for quite a while looking for the right code.

Thanks!

Mr. Jim

View All (5)

View All (1)

LabVIEW Idea Exchange

Ship NI Developer Suite on USB keys instead of DVDs

Inlineable property nodes / Invoke nodes when apporopriate

When closing project or quitting LabVIEW, Abort VIs dialog should list the VIs

Make default type of new controls: Type def

Application Control Items - Replace without disturbing the connected wires

Browse button for File Path constant

"View As Color Box" option on numerics?

Unbundle By Name ( Wiring )

Case structure with case sensitive/insensitive indicator

Bookmark Manager: Add VI Source (List of VI-Refs or Names) to Application Event "Bookmark Info Change"

Default Arrays ( numeric / string / boolean ) - Not to drop each time into array

A Menu Entry to Clear Variant Data

Create cluster out of selection

Add "open copy of example" button to the example finder

Append auto incrementing number to the file name if file already exists.

Include 'Transpose Array' method in the shortcut menu of a 2D array constant/control/indicator

Add visual context preview for "Choose Implementation" dialog for OOP

Make VariantDataType functions officially supported

Make the Error Ring Searchable

Auto-detect and install required add-on software automatically