On 12/7/05, erixtekila <[EMAIL PROTECTED]> wrote: > > Le 6 déc. 05, à 22:26, Scott Hyndman a écrit : > > > And just as a side note, I came up with an interesting idea today on > > how > > to emulate multiple threads in Flash. Just use more than one movie! > > Talk > > between the UI movie and the background worker movie with a > > LocalConnection object, and you're in business. No more UI lock. > > Yes why not. > Can you elaborate the concept a little ? > > There could be a TaskManager running in the background swf. > It handle the thread like objects and send output when the thread dies. > > But the background swf must have implemented the classes that the > thread must take care of. > Isn't it ? >
I think you are thinking of this as a formal, seamless threading, whereas I think what scott is saying is that if you need something to work totally independently then just put that code in a separate movie and use local connection to share information between the threads. I am working on something where I have been thinking of doing exactly that. In the super simple scenario there wouldnt need to be a thread manager. The background task is just a swf with no OS like threading support. So when you start it, it just keeps running. It doesnt die until explicitly told to do so (like when the user quits or something). Regards Hank > Cheers > ----------- > erixtekila > http://blog.v-i-a.net/ > > _______________________________________________ > 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
