LabVIEW Idea Exchange

About LabVIEW Idea Exchange

Have a LabVIEW Idea?

  1. Browse by label or search in the LabVIEW Idea Exchange to see if your idea has previously been submitted. If your idea exists be sure to vote for the idea by giving it kudos to indicate your approval!
  2. If your idea has not been submitted click Post New Idea to submit a product idea to the LabVIEW Idea Exchange. Be sure to submit a separate post for each idea.
  3. Watch as the community gives your idea kudos and adds their input.
  4. As NI R&D considers the idea, they will change the idea status.
  5. Give kudos to other ideas that you would like to see in a future version of LabVIEW!
Top Kudoed Authors
Showing results for 
Search instead for 
Did you mean: 

Option for Disabled Structures to Not Use Default Value for Unwired Output Tunnels

IMO, the Diagram Disable Structure causes bugs, because the output tunnels of the Diagram Disable Structure are set to "Use Default if Unwired", and the default values are very often not desireable, as can be seen in the screenshot, below:

 

 

See this blog article, for more details:

 

http://thinkinging.com/2008/05/11/the-diagram-disable-structure-causes-bugs/

10 Comments
jdunham
N/A
Absolutely.  This is a huge problem
TCPlomp
N/A

This could be extended to normal case structures. I think Ben has made the propostion to have a 'Default Values' case with for every tunnel a default value if the value is not wired in the executing case.

 

Ton

PaulG.
N/A
Indeed. I hate the default value cases anywhere. Convenient and easy to use but opens your code up to too many opportunities for errors. I suggest making it selectable - globally - in Tools>Options.
altenbach
N/A

(Ton, you might remember my suggestion from very (very!!!) long ago as quoted here.  I still think is is a good idea and I might write it up as an idea here Smiley Wink)

 

Back to this thread:

 In many cases it might be sufficient to simply have a group of data types (such as references, etc.) that are simply not allowed to have default outputs at exit tunnels because it would never make sense. An unwired output for these specific types would give a broken arrow no matter what the tunnel setting is. Such rules would probably solve 90% of the problems mentioned above without causing options bloat. Smiley Wink

 

Personally, I like default output tunnels in many situations, especially for booleans, strings and numerics. It simplifies coding. Smiley Happy

Ale914
N/A
i completelly agree this caused me to waste a lot of time in a past project
Ray.R
N/A

It would be great if it could look at the input tunnels and make an association with the output tunnels and make those values become default.  For non-matching tunnels, then they would not have default values.

 

Jim_Kring
N/A
Ray: I agree that it would be nice if some smarts were added.  I'd like it if LabVIEW could automagically wire the input tunnels to output tunnels if the vertical position and data type is the same -- and, perhaps this could be scoped to only happen for the error cluster and reference wires.
Ray.R
N/A

Thanks Jim,

 

You read my mind.  Smiley Happy

I wasn't sure if my post was clear, but it's exactly what you described. 

The default values would be whatever value is at the input tunnel.  The same as if they were wired through.  

 

R

tst
N/A
X.
N/A

Check Altenbach's suggestion here.