Closed vincentjames501 closed 10 years ago
It would be better - but building one-use arrays on every step is terrible for GC, which is the primary performance issue Quintus has, so it's a no go.
If you're running into a problem - call stage.remove(sprite) which will put off the call to destroy until after the step
The code below shows the problem
It would be better to build an Array of the functions you want to call, then execute them all so the list is immutable during iteration.