LabVIEW Idea Exchange

cancel
Showing results for 
Search instead for 
Did you mean: 
Darin.K

Make 'Disable Indexing at Source' a more useful option

Status: New

Under the right set of circumstances, a very useful Right-Click option appears on a broken wire 'Disable Indexing at Source'.  I'll wager that many of you have never noticed this option.

 

If you have an Array Primitive which is wired immediately to an auto-indexing tunnel resulting in a broken wire, you can right click the broken wire:

 

DisableIndexing.png

 

Not bad, but in this case you are right there to right click on the tunnel anyway.  If the autoindexed tunnel is one loop out, no luck.  If it is a subVI with an array input instead of a primitive, no luck.

 

I would like the following improvement to this potentially useful option: Make it work on any wire (broken or not) that has an autoindexed tunnel somewhere along the line.  If I have 5 nested loops I would like to be able to move to a wire 3 loops in, choose this option and have all autoindexing removed from that loop outward.  No more hopscotch, just one simple step when I want my array to be an array inside a few loops.

 

Right now I often drop While Loops and then change to For Loops after wiring, that just seems silly.

2 Comments
altenbach
Knight of NI

You win the wager. I never noticed the option you mentioned. 😉

 

It would also help already if we could select several tunnels at once followed by "disable indexing". How about holding a certain key, (e.g. alt) while wiring across the loop boundary(s) and the tunnel would be the opposite of the default mode (indexing for while loops and plain for FOR loops, etc.). "shift-alt" could create shift registers....

 

Under certain scenarios (not in your case described above), there is enough information to automatically select the correct tunnel option without user interventions. This goes along this old (ancient!) idea : Smart autocorrecting autoindexing 

Darin.K
Trusted Enthusiast
It would indeed be nice to select multiple tunnels and change to and from autoindexing. The alt key is tricky since it really is tied to Windows OS and I do not know what the Mac equivalent would be. You triggered another idea, what if you had to tack a wire to a structure (for or while loop) to get autoindexing while wiring directly to an internal node would not autoindex anywhere. All created tunnels would not autoindex. I may be the only one who likes it, but at least it is one set of rules.