Conveyed Items: Different positions for GetAt(i) and Delete(i)

[Viking]

Code: [Select]

for (short i = (short)(Conn.ConveyedItems.Count - 1); i >= 0; i--)
{
  ConvItem = Conn.ConveyedItems.GetAt(i);
  if (ConvItem.ElementGUID == Elem.ElementGUID) {
    Conn.ConveyedItems.DeleteAt(i,true); // same problem with false
  }
}
Conn.Update();

If I run this code, it does not delete ConvItem. It deletes another item in the collection. It only happens if ConveyedItems > 1. If there is only 1 item, everything is fine.

I never had problemes with collections before. I tried a lot of alternatives. That's why and because Geert Bellekens recommends it I report it as a bug.

See also https://www.sparxsystems.com/forums/smf/index.php/topic,44835.msg263969.html#msg263969

[qwerty]

A bug is not reported here but with the bug report in the Support section below.

q.

[Viking]

Conn.ConveyedItems.DeleteAt(i + 1,true);

This works. Maybe there is a rule, so that I can use it as an intermediate solution.

[Viking]

A bug is not reported here but with the bug report in the Support section below.
q.

Many thanks @qwerty. I did not know. This section is called "Bugs and Issues" ...

I follow your recommendation

[qwerty]

You're not the first one being mislead ;-)

q.

[Geert Bellekens]

Conn.ConveyedItems.DeleteAt(i + 1,true);

This works. Maybe there is a rule, so that I can use it as an intermediate solution.

You would get an index out of bounds if you tried that on the last item of the collection wouldn't you?

Geert

[Viking]

Conn.ConveyedItems.DeleteAt(i + 1,true);

This works. Maybe there is a rule, so that I can use it as an intermediate solution.

You would get an index out of bounds if you tried that on the last item of the collection wouldn't you?
Geert

That's true, Geert. The solution is much easier.

I report it in in the initial thread https://www.sparxsystems.com/forums/smf/index.php/topic,44835.0.html.