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:
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, 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 )
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.
Personally, I like default output tunnels in many situations, especially for booleans, strings and numerics. It simplifies coding.
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.
You read my mind.
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.
There's a similar idea for event structures here - http://forums.ni.com/t5/LabVIEW-Idea-Exchange/Output-tunnels-from-event-structure-should-default-to-...
Check Altenbach's suggestion here.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.