I’m toying around with something at the moment that’s working out quite nicely, but I’m getting worried about processor strain. It currently involves a grid of 1173 movieclips each with an onEnterFrame event. (Yes, I know that sounds mental, but it works).
Currently, I have an initialisation object which I associate with each movieclip when I attach is using attachMovie. I have then declared an onEnterFrame event for the initialisation object. My question is, are there any advantages / disadvantages of applying the onEnterFrame events seperately to each movieclip, compared to using a “general” onEnterFrame (ie _root.onEnterFrame) in which I cycle through each movieclip and do the neccessary calculations?
eg:
1173 onEnterFrame events running togther
VS
One onEnterFrame event that performs a loop of 1173 iterations
Is a loop of that length going to have any advantages against having 1173 onEnterFrame events?
This sounds ridiculous, but if anyones got any info on the subject and can actually decipher what I’m trying to say, I’d appreciate the help.
