From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.

We appreciate your patience as we improve our online experience.

LabVIEW Idea Exchange

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

It would be interesting to have something I could drop into the block diagram that would work like a navigation point. Maybe something I can route a wire through that wouldn't change anything about the data. You would could drop it in and give it a tag, then later pull up a nav points window that would list all of the nav points along with their tags and an optional description, and a way to double click one to jump to it. This would make it much easier to document code and navigate through large projects, especially projects with multiple developers.

You can hide a control on the front panel by right clicking and going to the "Advanced" menu:

Hide ctrl.png

 

It would be nice to have a corresponding way to un-hide a control, possibly in the "Advanced" menu when clicking on the control in the block diagram:

Unhide ctrl.png

 

Alternatively, you could make enable the right click menu on the front panel when you double click the control on the block diagram and it shows you where the hidden control is on the front panel:

 

Unhide ctrl alt.png

 

I often select a wire constant and use QD (ctrl-space, ctrl-i) to add things onto wires. When used with "insert into map", QD auto wires incorrectly.

 

BowenM_0-1616526386871.png

 

 

BowenM_1-1616526426198.png

 

BowenM_2-1616526476377.png

 

BowenM_3-1616526543430.png

 

 

Please provide option to select display style in string probing.

mrk_ramesh_0-1614662185638.png

 

Being able to initialize arrays as empty sets would be handy - not just as 0 or NaN.

It's kinda like opposite of "remove and rewire".

 

In some cases we need to insert two end function node to wire repeatly, for example I might need to insert a lot feedback node when debugging FPGA code.

 

Right now we need to select a wire, select function (4+ clicks or so?), let alone we have to move the mouse cursor.

 

It would nice if we can set a shortcut for these kind of operation, say, we might select a wire(or maybe more then one wire?), then we press like  Ctrl+1, we will automatically insert function 1 in this wire(s), which user could config themself.

 
 

When debugging a program, I'd love to have a node similar to the "abort vi" node that programmatically pauses execution instead of stops it completely.  You might say this is the place for a conditional breakpoint, but unless I create my own custom ones, it's hard to make something that breaks on, say, the third time an error of this type occurs.

 

I have places in the code where I throw an error that is fatal(-ish), but it isn't caught until much further downstream.  In order to find which of the many calling vis triggered this error, I have a few options:

 

1) I can list the call chain.  This works, but still takes until the point the error is caught by my error handler popup to actually list the full problem, and due to either programmer error or bad design, can sometimes be overwritten by other errors thrown and badly merged further down the line.

 

2)  I can delete the error wires throughout the program and ensure automatic error handling is enabled.  This pops up the problem immediately, but often I don't have enough context to know if the error is the one I'm trying to track down, and my only options are to continue or stop.

 

3) I can throw multiple conditional error probes or breakpoints throughout the program, which works, but both are ephemeral as most of the time they're cleared using the "delete all breakpoints" button, and probes are lost when you close the window.  I'd like a more permanent and preventative solution.

Hi Team,

 

A really small thing (and cosmetic...), but could you enable 'Adjust Pane Origin' for the block diagram, please? Since LabVIEW 19, there's an option to adjust the pane origin on the FP (Edit > Adjust Pane Origin

 

I would like the option to do that on the BD too as I like having BD dots on, but the origin looks out of place (unless I manually move the BD).

 

Adjust Pane Origin.png

 

For restructuring a larger application I created a VI that shall recursively replaces all missing VIs and type defs based on a lookup table.
For VIs this works fine but it does not work with missing *.ctl files (type def) for controls or constants because there is no "MissingTypeDef" property available.

I'd like to suggest to add something a "MissingXYName" property to each class type that refers to a file - corresponding to what the VI class is already offering.

In my personal opinion it would be even better to have a file-pathname property (which shall be valid even if the file is missing) plus a second property (enum) that shows if this file is valid or not (0: all fine; 1: there but somehow invalid; 2: missing).

 

Andi_S_0-1583930751196.png        Andi_S_1-1583930838129.png

 

 

In the spirit of Ctrl + double-clicking a subVI to open it straight to the block diagram, Ctrl + double-clicking a type def control / constant / indicator should open the type definition. Just a bit quicker and more convenient than right-click -> Open Type Def.

 

ctrl_dbl-click_typedef.png

I would like to see the filename of a type def appear when you choose visible - label.  Right now it just shows up blank.  I do not want to have to stop to type a unique name

 

.  Adding label to type defAdding label to type defAdding label to type defAdding label to type def

 

Using LabVIEW primitive Unflatten From JSON, we need to know the precise structure of the JSON input to access a specific value.

However sometimes we don't have the precise sturcture of the JSON input beforehand, sometimes the structure is heavily nested.

It will be very useful to parse JSON value, nested object or array as string, so that we can observe it or leave further parsing to a latter stage.

e.g. {"a":{"b":[{"c":"c"},{"d":FALSE},{"e":[1,2,3]}]}}

the structrue of value of "a" is a little complicated and I'd like it to be parsed into a string first. It would be very convinient if we can have cascaded parsings as shown below.

 

capture.PNG

 

Is there a way to change the provided glyph size in the Icon editor? If not I think this should be added

when stepping into a VI,

do not read controls before pausing

because latch value should not be reset prior to pause
and because debugging capability would be enhanced with ability to change control values at step in (like TS LV adapter)

When right-clicking an existing channel wire, the only channel option is to create a Channel Reader.  I'd find it helpful to be able to easily create a Channel Writer directly as well, working backwards to the data input.

Would allow to reduce the complexity and number of frames needed in a type specialization structure when the action is basically the same.

 

For example in the attached vim, the number [2] frame could be used for all number types and thus eliminate all the following frames.

 

2018-10-10_18-33-33.jpg

I hope it would help.

When create a subvi, can easy to do with press shortcut key such as Ctrl+Shift+V, instead of struggling to select from edit list.

 

Similar from these snaps,

 

Create SubVI.png    Create SubVI Sort.png

 

Whenever we add a new item in tree programatically using "edit tree item" node,

2018-09-15_1719.png

We are not sure what tag would be set to Child Tag. Because if that tag already exists LabVIEW will appends a number to make it unique.

From help of "Edit Tree Items:Add Item Method"

The default is the string you wire to Left Cell String. If an existing tag already uses that string, LabVIEW appends a number to the string to create a unique tag for the new item.

 

It would be great if we can get the value of "Child Tag" as output as well, which is set by LabVIEW.

I have VI's and projects saved in Chinese characters and they do not open in the English version of LabVIEW. LabVIEW is unable to read special character unless I change my system languages. I feel that LabVIEW should be able to read all different languages and not required to download different versions. 

I faced issues while creating an installer with a size of 2GB+. Unfortunately I had to upload the installer to a shared site that didn't accept files > 400MB. The want for a separate installer and process thereof delayed my delivery.

I remember from other software(s) having distro creation capabilities in size of lets say a standard CD size of 650MB, etc.

Wouldn't it help many if the app builder allowed splitting the installer in a defined packet size?