Nested loops index bug

[Royagers]

If you use nested loops, the last index is always used. Herewith, in design mode, different "current loop count" blocks are dragged.

Code: [Select]

/* ====================== Custom Event ======================= */
public function _customEvent_TEST():Void
{
for(index0 in 0...2)
{
for(index1 in 0...3)
{
trace((("index0:") + ("" + index1)));
trace((("index1:") + ("" + index1)));
}
}
}
This may be by design, but it would be better to use different indexes.

[Justin]

Yes, it's currently not possible to distinguish between two of these, so until this is handled in some way, you'll need to assign the outer loop index to another attribute.

[Royagers]

Ok.

 nested loops.png (18.17 kB, 326x189 - viewed 1612 times.)