If you have a Repeater element that contains the Options of a Choice object, you often want to synchronise the selected item in the repeater with the Chosen item in the Choice object.
One of the techniques to do this is using ChosenIndex - you can set the ChosenIndex of the Choice object to the RepeatedItemIndex that is found in the Repeater.
However, if your Repeater can repeat, the RepeatedItemIndex number keeps going. So if you move to the item after the last one (let's say you have 100 items in your Choice and Repeater and are moving from the 100th back to the first), rather than going back to '1', you instead get index #101 - which immediately crashes your program with an exception.
The same thing applies to going backwards. Rather than going to 100, it goes to -1.
Is this by design? Or is it a bug? If it IS by design, is there any justification for this sort of behaviour?