BD Array Constant cannot be "browsed"?

[X.]

I've been annoyed by this in the past and a quick search did not yield any answer, so here is it:

Is there a good reason why an array constant on the BD cannot be looked at, in the sense that the array index is no clickable?

For instance, I am parsing a header using an array of strings and while I am debugging the process, I'd like to rapidly check what the index of entry "this" or "that" is so that I can put some conditional probe that will get me there quickly. The problem is, the array is too large to be seen at once on the diagram. Moreover, what I want to do is bring the item I am interested in to the top of the list so that I can check its index:

 

The problem is, once I step through the code, the array is "frozen" and I can't play with the index control.

That should not change anything to the code, so I don't understand why I am prevented from doing that.

I can browse through cases of a structure or a sequence. Why not an array constant?

Tested in LV 2011, but has been here forever.

[altenbach]

You are specifically talking about run mode, right (in edit mode you can change the index).

You can show the scroll bar of the array container. It seems that still works in run mode, but I agree that the index should maybe also keep working.

[X.]

Excellent. I did not think about checking the scrollbar behavior... (and showing it in the first place).

[altenbach]

Of course the scrollbar is somewhat limited, bvecause you cannot scroll all the way to element 43 as shown in your picture.

[X.]

This is where I show something to a Knight:

🙂

[altenbach]

Yes, if you only want to see a single element at any give time, this will work. It won't work on your original array. 😉

[X.]

I agree. I'd rather have NI fix the array index control thing...