> Currently all the code assumes there's > > only one thread of execution. > >
There are good reasons for both cases, however, if Adobe insists on continuing down their threading model, they need to find ways to make it more friendly. For example, syntactical sugar for timers might be a good idea. Also, a way to execute long iterations without having to break up into timers seems doable - even if we have to sacrifice a few events along the way. How about simply going into modal / busy cursor mode as we execute those long cycles? It seems weird to me that I need to break things up into multiple calls just so I can avoid a "Not Responding" message.
