The load is asynchronous and should not block the UI.
However, intense, long proccessing will block the UI. A typical solution is to break the long process up into parts. Maube iterating i=_iIndex;i<_iIndex+10;i++ then set _iIndex and use callLater() to restart the incrementer. callLater is critical becaue it allows the UI to redraw before resuming the processing. But the Flash Player is essentially single threaded. Tracy ________________________________ From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Aaron Wright Sent: Wednesday, May 30, 2007 4:17 PM To: flexcoders@yahoogroups.com Subject: [flexcoders] What is the Flex solution to missing threads? I have an xml file that I load and parse. This parsing takes some time. It takes enough time that the GUI blocks momentarily. Normally I would send the xml parsing off in it's own thread but Flex does not offer me that easy of a solution. My question is, Is there a design pattern allowing long loops to not block the GUI. Flex being asynchronous is giving me some headaches.
