Moving from 206 to 212, I am finding my loops are broken. I ran through all of the releases up to 212, and the issue appears only in 212, presumably a side effect of the other loopindex fix. When iterating a double loop of X & Y, and calling a function which also iterates using the same variables, even though the loop iterates the correct number of times, using loopindex() returns the last values that the function had, from the previous call.
I suspect there may be other issues with this recent change, but this was the only case I could reproduce here.
Attach a Capx
Description of Capx
Iterate in "x" and also "y" which calls a function that iterates the same names.
Steps to Reproduce Bug
Run and look in CONSOLE for debug statements.
The outer loop works once, but after that, the outer loop only reports (via loopindex()) the last values set within the function's loop.
The scoping of the loop names/variables should revert back to the scope of the outer call.
Operating System and Service Pack
Construct 2 Version ID