LabVIEW Idea Exchange

Top Authors

User

Kudos

Post an idea

The High Resolution Relative Seconds VI has been around since LabVIEW 2010 and according to Darren is cross platform.

So what reason is there to not have this get more exposure on the palette? Admittedly I still use the tick count for just about everything I do, but I think bringing this function the Timing palette would help those who ask about more accurate timing needs.

The only argument I can see, is that new users of LabVIEW are going to want to wait X microseconds and turn a digital line high and low, and be confused when Windows isn't consistent. But this argument can be used for the normal timing functions too, because Windows non-deterministic.

Add subpanel property: VI Ref

Currently, you cannot get the ref of a VI contained in a subpanel. When removing a VI from a subpanel, the VI ref is not returned either. Having access to this ref would be useful so you can access the VI and stop it after you remove it.

The solution would be to add a "VI Ref" property node (read only), and/or return the VI Ref when using the "Remove VI" method.

This forum article describes the issue in more detail: http://forums.ni.com/t5/LabVIEW/Given-a-VI-can-I-determine/m-p/790441?requireLogin=False

LabVIEW allows us to create VIs in classes and call those VIs by using property nodes. This is very convenient for writing the code, but when running and debugging, there's no way of directly accessing the VI.

To resolve this, LV should have an option of opening that VI, for instance by right clicking the property:

This should probably also work when the VI is running and should probably open the dynamic dispatch selection dialog if the VI is a dynamic dispatch VI.

View All (1)

Automatically Create Terminals

View All (3)

Quick VI icon creation

The icon editor introduced in 2009 makes creating a VI icon faster, but there is still some room for improvement. Often, creating a VI icon simply means putting some text on the icon.

What would happen if we had a very quick way of doing this?

IDEA - add a button near the icon which will automatically generate the icon based on the VI name:

Clicking this button will automatically generate an icon with some text (and possibly glyphs as well?) based on the VI's name.

Don't like the icon? Click the button again and the algorithm will try a different version. Maybe over time the algorithm can learn your preferences.

Note - this idea is based on part of this one. Also, note the sly reference to this one.

We need to be able to search/filter event sources when adding a new event.

When you have a lot of controls/indicators in complicated nested structures, some of them will have the same names on the lowest level, It is very time consuming to visually scan through all the name to select the control for new event.

Current type to search functionality finds only lowest level control names which is not helpful. In the example below it will not find "Frequency" if I typed it, but it will find only "X" or "Y", but if there are 200 of them it is useless.

View All (7)

Locked Arrow Decoration

In short: The delete row/column option in the right-click menu of listboxes should also allow you to delete all rows/columns (or "Clear Items List") in one go.

I typically get into this problem if I am filling a listbox with items programmatically. Before I save the VI and distribute it, I do not want it to contain all those items. I want it to be empty. So I right-click on the list and expect an option to clear the items list, but the only option available is to delete one row or column at a time. An impractical if not impossible task if the list is of any size. Today I end up doing it in code. I run the code once, remove it - and run into the same problem after the next run and save...

Example:

PS. This is a good candidate for JKIs Right-click framework too, but I think it deserves a place in the in-built menu.

Change the Path Type function output from a signed 16-bit integer to a text ring or enum to aid immediate readability of code and save having to look at the help file:

The Path Type function returns a signed 16-bit integer indicating the following 3 types of paths.

0: Absolute path

1: Relative path

2: <Not A Path>

Unhelpful context help.

Text ring would have the least impact on existing primatives: https://forums.ni.com/t5/LabVIEW-Idea-Exchange/Path-Type-Function-needs-another-return-for-an-empty-path/idc-p/2588549/highlight/true#M25086

There has been a lot of discussion on this but no LabVIEW Idea (that I was able to find). Please move the Stacked Sequences from the Programming Palette to a "retro" or "classic" palette. This is dissuade novices from overusing them

Previous wording:

There has been a lot of discussion on this but no LabVIEW Idea (that I was able to find).

Retain them for legacy code but please remove them from the Programming Palette

Lets vote this in and get rid of Stacked Sequences forever.

I would go so far as to release a patch to remove them from all Installed LabVIEW Versions!

Message Edited by Laura F. on 09-30-2009 03:49 PM

View All (1)

When configuring FXP datatype, the range, max, and delta are shown with a resolution of only four decimal digits. This is not enough!

(For example, look at a type with 12 fractional bits. While the delta is 0.000244141..., it shows up as 0.0002, which is off by over 20% and could give the false impression that we have a nice round decimal delta)

Silly enough, the indicator field is 60% blank. There would be plenty of room to show more information and the indicator could even be enlarged and still fit inside the box.

The insert in the figure shows how it would look like with a display format of 6 significant digits. Seems to be much more realistic!

IDEA: Show more significant digits for the range indicators of FXP configuration!

In addition, the current "desired delta" indicator should be renamed to "Delta".

It is an indicator, so we cannot enter anything we desire anyway!

The delta is a result of the binary limitation of the configured bits. It is what it is! The word "desired" might raise wrong expectations! 🙂

View All (4)

I do this in almost all screens that are meant to be user interfaces. I assign the tabbing order & then check the 'Skip this control when tabbing' for Error In control. So it would be nice if this option is checked by default for an Error In control.

Thanks,

Priyadarsini S

View All (2)

View All (6)

View All (4)

I always use "Find All Instances" for searching where a subvi / control is used.

When looking into code that is locked (read-only because of being under source control), this option is missing!!.

Now I always have to press Ctrl-M to Unlock, then press change on the next dialog

before the "Find All Instances" becomes active
Or open the VI Hierarchy (could take a while on a large project)
and here the normal right-click "Find All Instances" is not blocked!!

I don't think it should be a big problem to enable the right-click menu on a locked vi...

View All (1)

LabVIEW Idea Exchange

High Resolution Relative Seconds on Palette

Add subpanel property: VI Ref

Add option to open LVOOP accessor VI from the property node

Array scrollbar "scrollable" with scroll wheel

Automatically Create Terminals

Make project window dockable and always on top

Quick VI icon creation

Event structure: ability to search/filter sources

Allow the "Find All Instances/Callers/SubVIs" Window to be Resized

Locked Arrow Decoration

Delete All Rows/Columns in Listbox (Clear Items list from control panel)

Path Type Function - Return text ring or enum instead of plain I16

Move Stacked Sequences from the Palette

Fixed-Point (FXP) configuration needs to show more decimal digits

Place Terminal in a Floating window on Block Diagram when new Control/Indicator created

Error In control should have key navigation skipped by default

Add Select Area - Move Area feature to Icon Editor

TDMS function to delete channels and groups

(sub)VI-Icon: make "Find All Instances" also available when VI is locked (Read-only)

one click save control as typdef