LabVIEW Idea Exchange

[#1]

When autoindexing on a WHILE loop input tunnel, we get the default value for the datatype after we run out of elements on the autoindexing array. I can think of several scenarios where it would be useful to simply start over with the input array.

I propose a new input tunnel type (looping) which would do exactly that: index the elements to the end of the array, then start over from the beginning, ad infinitum (or until the loop stops).

(The same would of course also be useful for FOR loops. Here it would not be used to determine the loop count, because it never runs out of elements.)

Here's how it could look like in the code. (On the right, I show explicit functional equivalents).

[#2]

Note that I use the audio terminology of looping, which might be confusing because we already have loops in the code. I think it is OK, but I am of course open to better naming ideas.

• looping?
• recyling?
• repeating?
• reusing?
• ...

[#3]

Since it is still indexing the array I'd like to see the "index" stay..

• infinite index?
• looping index?
• repeating index?

[#4]

+1 for repeating index... to matching autoindexing, lets call it repeat indexing

[#5]

I was thinking Looping Index

[#6]

This is similar to the concept of a circular buffer, so you could call it circular indexing.

[#7]

Circular is definitely my vote.

Also, cool Idea! Not sure when I'll use it, but I definitely like it.

[#8]

This is useful for any case where there is some indexing action and it is not exactly terminal/wire related but rather index related.

I could have offered a change to the idea where we have a property node to the index terminal in order to create a secondary sub index terminal but it won't be general enough as well.

The most general option is to add a general cyclic block (wraps the reminder for easy of use) and to incorporate the conditional auto indexing tunnel in a more sophisticated way that handles cycles among other things in a pop up wizard once the tunnel is double clicked.

[#9]

I could definitely see this being useful if doing some sort of simulation.

[#10]

I vote for "Circular" too -- fits with the symbol as well.

[#11]

altenbach, can you enumerate some of the use cases that you have for this feature? I'm guessing you have some sort of "control this hardware" scenario in mind where you keep iterating over the same list of commands?