That is kind of what we do. We have a Command interface that all tasks extend. Then we have a queue that we add these tasks to. On each frame/interval we process the next item in the queue. We only do this for larger processing kinds of tasks, things that could take longer than a few milliseconds on a reasonable machine.
--- In [email protected], "Ralf Bokelberg" <[EMAIL PROTECTED]> wrote: > > Hi Tim > > How about splitting up your huge task (i'm just guessing here) and let Flex > decide, when it is ready to run the next portion of it? If you use a Timer > or setInterval is should work like that. > > Cheers, > Ralf > > On 5/2/07, Tim <[EMAIL PROTECTED]> wrote: > > > > Why aren't we allowed to tell flash to process the UI event queue > > periodically in long executing subroutines? > > > > Hell, just something to tell the client not to go into "Not > > Responding" would be more than enough. I call "validate now" > > periodically, but that doesn't help because I still get the "Not > > Responding" which makes it look like the software has crashed - a very > > awkward user experience. > > > > It seems like such a trivial thing for Adobe to add. Why don't they? > > > > > > > > > > -- > Ralf Bokelberg <[EMAIL PROTECTED]> > Flex & Flash Consultant based in Cologne/Germany > Phone +49 (0) 221 530 15 35 >
