LabVIEW Idea Exchange

Top Authors

User

Kudos

Post an idea

Do Not Save Option

View All (1)

Idea Exchange: LabVIEW Roadmap

One improvement that I can see helping both idea suggesters and moderators: Help us know the scope of potential LabVIEW change.

Many ideas here are marked complete because they've been implemented in NXG. (Samples 1, 2, 3)

The message I get from this status is, "That's a great idea. We'll put resources toward making our next-generation product do that awesome thing, but it's more work that we want to do on the current generation product."

Many others are marked declined because significant changes to LabVIEW aren't planned (presumably in consideration of end-of-life). (Samples 1, 2, 3)

The message I get from this status is, "That's a great idea, but it would cost us more than we want to put into our current-generation product."

I think both of those messages are totally valid, but I find myself increasingly reserved about suggesting ideas here because I don't know where those thresholds lie. Could the community receive some guidelines on what type of change might make it into LabVIEW? If we had those guidelines, we could save our own time by only suggesting things that might make it in and we could save the moderator's time by reducing the number of ideas to have to process.

View All (4)

I'd like to be able to delete an object from an existing wire and then have that wire be automatically reconnected. Currently a broken wire is left after deleting something and one must manually reconnect the wire. This would be the opposite of the popup option to Insert something. Some deletions may produce a maze of broken wires that would be difficult to determine what to auto-reconnect but perhaps situations where there is only one broken wire (for example removing a Numeric Increment function (+1) from a wire) could be handled.

View All (1)

I'm making Icon Templates out of the styles of icons I use most, and discovered it would be very useful if I could create a template and change one glyph layer for each template.

In the example below, I could load the Q Ref template, quickly remove the Q Ref layer and replace it with another control glyph.

I do realise I could just select the pink box and delete, but not all glyphs are nice easy to selct shapes and sizes

The templates with layers should be seen with the other templates, but when selected, recreate the individual layers in the layers tab

View All (2)

Insert compatible VI into flow

Let's uppose I'm sending a sequence of commands to a VISA-controlled instrument (see picture).

While dubugging, I realize I missed a command along the sequence (on following example, I forgot setting output impedance):

As of now, I need to delete the wires between 2nd and 3rd VIs, place the missing VI, then draw the four missing connections.

I'd like Labview to recognize that the I/O pattern of the VI to be inserted is compatible with the existing flow, and to insert it correctly.

Something similar already happens when you place a new VI into the block diagram, and you drag it near a VI with compatible I/O (blinking wires appear).

View All (4)

Case insensitive searching in maps

View All (4)

Asyncronous Call By Reference

Here is an idea that I have wanted to make happen for a while. It is the Asyncronous Call By Reference. Basically, it is just a Call By Reference, but split in half so that the call is not syncronous (blocking), and return data can be obtained from multiple locations. Plus, there should be ways to check the status of the asynchronous call and kill it. I've even implemented this, to some degree, here http://forums.openg.org/index.php?showtopic=88

Message Edited by Jim Kring on 06-10-2009 08:14 AM

View All (2)

Currently the lvsound2 library -- the Sound Input and Sound Output VIs supported by lvsound2.llb and lvsound2.dll -- updates the audio device list from the operating system only when first being loaded into memory. If you change the device list (e.g.., pair/unpair a Bluetooth headset) the device IDs will not reflect the new configuration until all the lvsound2-dependent VIs have been unloaded from memory. After adding or removing a device, the VIs will generate error 4803 ("The sound driver or card does not support the desired operation.") for device IDs related to the new/removed device, even if the ID is still actually valid and points to something else. This is extraordinarily inconvenient for test systems focused on audio device testing, but understandably a niche issue, which may be why it hasn't been caught before now.

In the interim, the workaround is to dynamically call any of the VIs you're interested in to force them to load/unload as necessary. There are two appropriate solutions I can think of:

1) Update the Sound X VIs to implement the dynamic call workaround (preferably directly around lvsound2.dll calls so we can still borrow other VIs in the LLB).

2) Update the DLL to support on-the-fly changes.

The latter solution is ideal, particularly for performance. This reads both as a suggestion and a bug report so that anyone else who has this problem can find a public forum documenting the issue.

View All (2)

In LabVIEW 2013 a new feature was introduced, the arrow connecting free text and code objects. However when you try to route a wire trough the arrow the LabVIEW routing goes nuts and try's to avoid the arrows at all cost.

A picture to show what I mean:

The highighted wire (yellow-red) is routed from "Start Location" to "End Location" by LabVIEW. However I would like to see somehting more like the blue line since this makes more sense. If I want the blue wire I have to manually move the wire since the rouring can't handle the arrows of the free text boxes.

View All (1)

"Restart LabVIEW" menu item

Custom events for XControls ...

It should be nice to be abble to add Custom events to Xcontrol ...

I know that it is already possible ... but in a not user friendly way !

I would like to be abble to add a custom event like adding a new property or a new method.

And this "Xcontrol user event" could be seen automaticaly in the "Add new event" of an event structure, when an instance of this XControl has been drop on a front panel.

So what i would like is ...

Adding a custom event to a Xcontrol, as a property
That this Event appears automatically in the event structure configurator. (Like events of standards controls and indicators)

My need is to add custom event different from "Value changed", in order to build powerfull XControl.

And be abble to use these events without having to regiter them manually. (But like standards controls and indicators)

View All (3)

LabVIEW Idea Exchange

Do Not Save Option

Idea Exchange: LabVIEW Roadmap

Trigger XControls for Dynamic Events

Delete object from wire and auto-reconnect wire

Icon Editor Saves Layers in Icon Template

LTS (Long-term support) vewrsion of LabVIEW

Insert compatible VI into flow

Radio Button Boolean Text Should be Off By Default, Especially for a Radio Button Group

Case insensitive searching in maps

Add Support for Array of Array

Asyncronous Call By Reference

Save as and "open additional copy" - Close original VI

Preview FP option for non runable VIs

Update the lvsound2 library (Sound Input/Sound Output VIs) to support changing audio devices on-the-fly

Define events triggered by XControls

Allow the wires to go trough the arrows of free text

Call Library Function Node needs more Visible Items

"Restart LabVIEW" menu item

Custom events for XControls ...

Flatten to JSON - Allow any data type on the "anything" input