Convert valid Shift Register to Non-Auto-Indexed Tunnels

[GregSands]

Reading this idea on auto-Shift-Registers, I thought of another use case that seems to be implemented wrongly.  When selecting "Replace with Tunnels" on a valid (i.e. wired and not broken) Shift Register, then the tunnels should be created as Non-Auto-Indexing so that the code remains unbroken.  However, if the Shift Register contains an array, then there should be the option on the right-click-menu to create either Indexed or NonIndexed terminals, as either may be wanted.

[tst]

Frankly, I think this case is a lot less clear cut and a lot rarer than the other one.

Adding a for loop around existing code where part of it should not be changed is something I do relatively often and there LV almost always gets it wrong.

Replacing an SR with a tunnel is something that's a lot less frequent and where a non-indexed tunnel is often the valid answer. I don't feel I need a shortcut there, as it would also just blow up the menu.

[Intaris]

I agree with tst here.  I don't see it as important enough to warrant inclusion.

[GregSands]

I thought I was saying the same as these comments, but perhaps it wasn't expressed clearly!  The main idea was that the default should be to create non-indexed tunnels -- as you say, this is the "logical" solution, and most often wanted, so it's not a matter of adding shortcuts, just changing the default behaviour to what is most intuitive.  The reason for linking it to the other idea was that I realised that if Shift Registers were automatically created when inserting a For Loop, then changing them back to tunnels was something that I'd do more often than at the moment, and I didn't want to have to deselect the auto-indexing every time.

I added the last comment once I realised that for arrays, you may not want that by default.  But I'd be more than happy to have no changes to the menus, just the default behaviour changed.

[tst]

That I agree with - if you have an array going into a SR and you replace it with a tunnel, non-indexing should be the default and I didn't realize it isn't that way today (because I don't do this operation often). I suggest you create a new idea instead of this one where you make it clear what the behavior is today and what you want the new behavior to be. Images also help.

[NJKirchner]

https://decibel.ni.com/content/groups/labview-apis/blog/2013/04/01/for-loop-pass-through-utility

This might help a little, although not everything you've dreamed of

[Darren]

Any idea that has received less than 5 kudos within 5 years after posting will be automatically declined.