The program croaks when measureContentArea (in package
mx.containers.utilityClasses, file CanvasLayout.as ) loops through
the target's children from 0 to target.numChildren. When the
program errors: n == 1, i == 0, and target.numChildren is now 0,
when it was 1 before the loop. target.numChildren has changed while
the loop is running. It's as if a child was removed by some side
effect of calls in the loop.
This happens even when I have many IOComponents on the
This baffles me because I don't see how I can debug it. I do
add and remove and insert children in my game code, but unless
ActionScript is threaded I don't see how my code can reach into a
loop in CanvasLayout.as .