There is some truth to this, but parf of good architecture is about tailoring what you have to what you need. In my current application, I have a collection of data that needs to be processed. Under certain circumstances I actually get the dialog box about the app running slowly.
So what I did was to make this data processing "chunkable", and then I use setInterval to calculate pieces of it at a time. I was thinking about the concept of a separate swf but this turned out to be easier. So I guess my point is just that threading would be nice. I use it sparingly in my java side work. But I do find that it is generally possible to do what you want to do in a single threaded flash player. Regards Hank On 12/12/05, Meinte van't Kruis <[EMAIL PROTECTED]> wrote: > I don't see how UI lock can be effectively solved using actionscript. It > seems to me multithreading in AS would be very fancy, and anything fancy > that isn't native just slows things down even more in my opinion. > > On 12/8/05, Mike Britton <[EMAIL PROTECTED]> wrote: > > > > It scares me too, but so does UI lock, something that's been happening > > to me a lot lately. > > > > Mike > > _______________________________________________ > > Flashcoders mailing list > > Flashcoders@chattyfig.figleaf.com > > http://chattyfig.figleaf.com/mailman/listinfo/flashcoders > > > _______________________________________________ > Flashcoders mailing list > Flashcoders@chattyfig.figleaf.com > http://chattyfig.figleaf.com/mailman/listinfo/flashcoders > _______________________________________________ Flashcoders mailing list Flashcoders@chattyfig.figleaf.com http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
