Manish, Thanks that's more like the info I was looking for. Just some details as to how Flash events and frame rates work in relation to callLater(). Using a timer has one distinct advantage that you can control how fast something is running where my technique ran every frame (or so I thought). Right now the processor is being killed so maybe if I use a high cycle timer I can control that better.
Charlie On Tue, Dec 23, 2008 at 11:16 AM, Manish Jethani <[email protected]> wrote: > On Tue, Dec 23, 2008 at 7:05 PM, Charlie Hubbard > <[email protected]> wrote: > >> The parsing of the XML is done separately from the iteration, and >> each iteration of the loop over the nodes is done using >> UIComponent.callLater(). So my algorithm looks pretty close to >> something of this form: >> >> function doIteration( currentIndex : int, totalIndex: int ) : void { >> var current : Object = objects[ currentIndex ]; >> doSomething( current ); >> callLater( doIteration, [ currentIndex + 1, totalIndex ] ); >> } >> > > You should consider a timer-based approach rather than a frame-based one. > > I remember looking at this library and thinking it was nice: > > http://blog.generalrelativity.org/?p=29 > > Oh, and I believe the Flash Player drops frames if it can't keep up. > Some more gyaan on this: > > http://www.kaourantin.net/2006/05/frame-rates-in-flash-player.html > > -- > manishjethani.com >
