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
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)