Make autoindexing tunnels conditional by default, and make condition optional

[Darin.K]

Now that the performance issues have been dealt with, I really like the conditional autoindexed tunnels in LV12+.  A bit too much of a right-click dance to get there, and I think the feature is a bit hidden and easy to forget.  Two tweaks to improve this:

1) All autoindexed tunnels should be conditional by default. 

2) The condition should be optional (it is currently required).  An unwired condition should be treated as true, ie. a simple autoindexed tunnel.

That little conditional terminal isn't hurting anybody, except that right now it breaks your VI until it is wired.  That is why it should be optional IMO.  Users who figure out what that terminal is after seeing it the first time, you are more than welcome, enjoy it.

There could be an option to turn this off, but I think it should be opt-out and not opt-in.  New users can learn the feature, others who know their way around can turn it off if they are so inclined.

[altenbach]

There should also still be an option to "hide" the autoindexing terminal if it is not used. It takes a lot of space and would be in the way if I autoindex several outputs from a subVI, for example.

[Darin.K]

Completely agree that it should be hidable.  

[X.]

Please don't. Conditional indexing forces autogrow in dense diagrams and that ripples throughout the diagram:

 ---> add conditional indexing---> 

Make it an option (more options for more power to the user!), fine with me.

[Darin.K]

I actually suggest the option to opt-out of this.  Personally, most times I would not care if it is there.  However, the number of times I want the conditional terminal far exceeds the number of times I would really want to hide it to pack terminals in.  I would much rather hide the conditional terminal a few times, than have to turn it on many more times, so long as it does not break my code in all of the 'don't care' times.

The ripples you mention are a direct result of creating overdense BDs IMO.  I understand that you choose an ugly color for the BD and are therefore motivated to cover as much of it as possible.  I have found that by enjoying a little white space (or yellow) on the BD means that I code faster, I re-code faster when it is time to change things, and that things can grow by a few pixels here or there without propagating to the entire diagram.  Basically I provide regions for damping the density waves which result from adding a new object.  You are creating that traffic jam that last for hours after the accident has long been cleared.