Home Community Idea Exchange LabVIEW Ideas : New Ideas

LabVIEW Idea Exchange

Community Browser
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Post an idea
5 Kudos
James_R

Change element of cluster with get and set methods

Status: Declined Submitted by Active Participant on 06-03-2009 10:46 AM 1 Comment

I like to dynamically control subvis with the get and set control methods

 

what would be nice is to get or set a single element of a cluster by naming it similar to a structure element in C

 

ex.    cluster_element.jpg

Labels:
7 Kudos
JB

Application Builder : add "Allow user to resize window" VI property

Status: Declined Submitted by Trusted Enthusiast on 06-03-2009 08:50 AM 2 Comment

Application Builder property dialog >> Source File Settings >> Customize VI Properties...

 

One property I'm really missing is "Allow user to resize window". Obviously it can be set in the VI itself but there is no way to overwrite this setting when building the application.

 

Resize Window VI Property.jpg

 

Labels:
4 Kudos
JB

Icon Editor

Status: Declined Submitted by Trusted Enthusiast on 06-03-2009 08:03 AM 8 Comment

Some more powerful icon editors (eg this one) have been written by users. An official version would be much appreciated.

Labels:
4 Kudos
Ian_Phillips

Allow Array to be directly wired to number of interations in FOR Loop

Status: Declined Submitted by Member on 06-03-2009 05:46 AM 2 Comment

Allow Array to be directly wired to number of interations in FOR Loop.  Right clicking number of interactions "N" would allow user to select Array dimension.  The demension could be displayed as shown.  This removes the need to "array size" and "index array" functions. 

For loop - old.jpg

For loop - new.jpg

Labels:
6 Kudos
Mads

Arrays with no spec between elements

Status: Declined Submitted by Active Participant on 06-03-2009 03:03 AM 4 Comment

Building multitype tables would be relatively simple using arrays of clusters...if it had not been for the fact that there is always space between the elements - causing the table to look unnaturally spread out.

Labels:
7 Kudos
Mads

Graph componants that actually fit together nicely

Status: Declined Submitted by Active Participant on 06-03-2009 02:49 AM 1 Comment

Create a graph and display all its legends, the graph palette, X scrollbar etc. - you now have a rather messy mix of objects that are quite difficult to arrange together or in a compact and stylish manner.

 

The sizes of the objects should be made to match in different arrangements (preferably compact ones) and their default positions should be a good starting point, not a mess.

 

You could also have different layout/style options so when you choose to create a graph you get a number of layout alternatives to start from...kind of like the way you get in Excel.

Labels:
3 Kudos
Vinny_Burzi

Suspend When Called Manager

Status: Declined Submitted by Member on 06-02-2009 08:35 PM 2 Comment
I would like to see a Suspend When Called Manager added to the development environment.  The functionality would be similar to the Break Point Manager (which is great).  When you open the Suspend When Called Manager it would allow you to see all VI's in the heirarchy that have Suspend When Called enabled and allow you to disable it.
Labels:
3 Kudos
Venkat Raghavan

Case Statement "Retain Current Value"

Status: Declined Submitted by Member on 06-02-2009 11:32 AM 4 Comment

When you pass a wire from within a case structure to outside a case structure, you have an option of "Use default if unwired".

 

If we had additionally an option for "Retain Current Value", this would simplify and prevent needless wiring, especially if we are using the state machine pattern. See images below for use case.

 

Case 1.png

case 2.png

161 Kudos
altenbach

A universal conversion bullet.

Status: Declined Submitted by Knight of NI Knight of NI on 06-02-2009 10:54 AM 16 Comment

My goal is to reduce palette bloat!

 

Let's look at the conversion palette. Certainly looks impressive, but why do we need so many different bullets??? They are basically all the same function:  A universal input and an output type.

 

I suggest that the 16 marked bullets on the image, plus some others (e.g. "to variant"), be combined into a single universal bullet where we can select the desired output type by a simple right-click. Whatever we select will determine the actual icon, so once things are in place, everything will look exactly as before.

 

When we first drop the universal icon on the diagram (or insert it into a wire), the context menu appears and we must select the desired output.

Labels:
6 Kudos
lvABC

Option to Scale Font

Status: Declined Submitted by Member on 06-02-2009 10:06 AM 3 Comment
I would like to see Option to Scale Font when FP resizes for all Objects or at least right click menu option for each object.
Labels:
View All (3)
6 Kudos
Punjab

Stacked Sequence

Status: Declined Submitted by Member on 06-02-2009 09:13 AM 18 Comment

Why we should not be able to add shift registers to stacked sequences becuase it will eliminate the break of direction of data flow due to sequence locals.

We should be able to put data to shift register in 1st frame and access it in next frame.Sequence Structure.jpg

View All (1)
0 Kudos
Olivier-JOURDAN

Close every probes in one click

Status: Declined Submitted by Active Participant Active Participant on 06-02-2009 08:49 AM 5 Comment
Add a modifier key when we close one probe (CTRL for example) will close every probe.
Labels:
View All (1)
1 Kudos
Marc Blumentritt

Expand Event structure functionality: conditional events

Status: Declined Submitted by Member on 06-02-2009 05:41 AM 2 Comment

Hello everybody,

 

(as suggested I will separate my idea Expand the functionality of Event structures into four seperate ideas to allow giving kudos separately.)

 

Make it possible to add conditions to events, e.g. only allow event foo, if condition bar is True. I'm not sure, how this should look like. Some static conditions could be "key pressed == a" coupled with "key down" event. Conditions could also be coupled to controls via registering the control reference like dynamic events. If my idea Expand Event structure functionality: Register new types of references is realized, a condition could also be something like "tcp/ip connection is offline". If a condition is not fullfilled, than either nothing happens or there is a leftside node, which indicates the status of the condition. This should be configurable.

 

Regards,

Marc

6 Kudos
Marc Blumentritt

Expand Event structure functionality: control of event buffer

Status: Declined Submitted by Member on 06-02-2009 05:36 AM 2 Comment

Hello everybody,

 

(as suggested I will separate my idea Expand the functionality of Event structures into four seperate ideas to allow giving kudos separately.)

 

Allow for better handling of the event buffer for fired events of Event structures. I would like to have a feature to list and remove item(s) from the buffer of fired events. Otherwise you have always to write some code to catch events, you d'ont want just to execute or you want to remove, because you just pressed the stop button. This could be realised by new leftside and rightside nodes inside the event structure.

 

Regards,

Marc

2 Kudos
jdunham

Index Array with required inputs

Status: Declined Submitted by Member on 06-01-2009 02:32 PM 4 Comment
The Index Array function should have an option (possibly default) to require that the index be wired. Forgetting to wire it up is a very common source of bugs and it's hard to find.  The autoincrementing feature when you grow this function is cool and should be preserved, but 95% of the time, I need to have the index wired in.
Labels:
90 Kudos
tst

Adding a "(don't) wait until done" option to the Call By Reference node

Status: Declined Submitted by Knight of NI Knight of NI on 06-01-2009 02:20 PM 8 Comment
I would love it if the Call By Reference node had a "don't wait until done" option, so that we can stop using the inconvenient and inelegant Set Ctl Val method or other inconvenient ways to pass arguments to dynamically called processes.

 

I believe the main issue with this is what to do with the outputs from the subVI (since you won't be able to use them) and I can think of two options:

 

1. This option would be settable at edit time and would break the caller if you wire any of the outputs.

2. This option would be settable at run-time and you would get default data from the outputs and an error or warning from the error out terminal of the node if you wire any of the outputs.

Labels:
View All (4)
1 Kudos
jdunham

Easier Access to terminal pane connectors

Status: Declined Submitted by Member on 06-01-2009 02:01 PM 1 Comment
Right now a left-click on an icon connection pane with the operating tool (the finger tool) just highlights the connected control or indicator.  It would be much more useful to have a drop down with the most common choices, especially the required/recommended/optional/dynamic dispatch selection.
Labels:
494 Kudos
Vinny_Burzi

Probes for Loop Iteration

Status: Declined Submitted by Member on 06-01-2009 08:48 AM 19 Comment

I would like the ability to probe the loop iteration terminal ("i" in For and While Loops) without the need to wire it to something (indicator, edge of structure,...).

Labels:
View All (3)
35 Kudos
TCPlomp

Define events triggered by XControls

Status: Declined Submitted by Trusted Enthusiast on 06-01-2009 02:03 AM 2 Comment

I think it would enhance the usability of XControls if it is possible to define events that an XControl can generate and that can be statically linked to just like other control type-specific events.

 

Earlier discussions on this topic has been done on LAVA and LAVA.

 

Ton

Labels:
View All (2)