LabVIEW Idea Exchange

It's very rare for me to deal with large arrays, so it's seems very retarded when I'm debugging to 

find VIs have not retained their values. I must turn on the "retain values" and re-run and go through 

a huge test sequence again to trigger the problem.

All to save 100K of memory, when I've got 2G to through around.

How about a global setting "RETAIN WIRE VALUES" and per-VI setting to override the global.

Wouldn't take much...

Wow,

This would be super powerful.

It's a little hard to grasp at first.

If you have sheets or tabs like EXCEL, you could write clean code in small chunks without have all the overhead of many SUBVIs!!!!!

I would use "local variables" to get data back and forth from different tabs/sheets.

TAKE 1 MINUTE TO THINK ABOUT!!!!!!!!

I've had case statements with 50 items.

It needs better tools

1. Delete cases in popup

2. Rearrange more than one case in the popup before it closes

Problem: Sometimes, we really need to keep pieces of code together during cleanup.

Current Solution: You can force LV to do this by putting a "sequence" around it. 

Bad Effect: Those are ugly, distracting, and suggest complexity when there isn't.

SOLUTION: We need a nice clean light grey box that does nothing that we can wrap around code snippets.

MINOR CHANGE, HUGE DIFFERENCE.

If you want to use the 'Call By Reference' node to call a VI, you have to provide it a strict VI reference.  Today, the only way to get a strict VI reference is to request one with the 'Open VI Reference' function:

But it is common to get a VI reference in some other way, like it being passed in through a control or obtained from other VI Server methods/properties.  We should be able to use the 'To More Specific' node to convert a plain VI Reference into a Strict VI Reference, like this:

If the reference does not have a matching connector pane, if the VI cannot be reserved for run, or if any of the other things that can go wrong with creating a strict reference happen, the To More Specific function would return an error on the existing error terminal.

In text based language, define some constants with meaningful names are very common task. For example, you typically define constant in C like this: 

#define RED          1

#define GREEN      2

#define BLUE         3

In LabVIEW, you can use ring to define them: 

and then you can use the constant very simple: 

But the following definition can not be implemented with ring:

#define RED          1

#define GREEN      2

#define BLUE         3

#define DEFAULT   1

Here, DEFAULT is the same with RED.  But this is not permitted by ring, it will popup a warning if you try to do this: "Waring: Identical values in the Values list are not permitted. The oblject cannot be updated until you assign new values or remove items with identical values. "

I know you can use local or global varibles to define constant as a work around, but variables have performance overhead, it is not the best solution as a result. 

I propose to create a "const" that allow different items share the same value, and the other behaviours will be the same as a ring. You can also add "picture const" and "text & picture const". 

The following topic on NI discussion forums inspires me to propose this idea.  

 http://forums.ni.com/ni/board/message?board.id=170&thread.id=435687