Calllater, intervals and what not are good for long iterations. Sometimes you want to run a deep recursion and that's harder to flatten. The Player Team continues to reject this idea. I think it is because it is non-trivial to implement as it means that a mouseevent could be processed before the mouseevent that called doEvents finishes and that makes somethings in the player more complicated. -Alex
________________________________ From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Jim Grinsfelder Sent: Wednesday, May 02, 2007 2:00 PM To: flexcoders@yahoogroups.com Subject: RE: [flexcoders] Why aren't we allowed to process the event queue? (eg: like DoEvents) Maybe we already can tell flash to process the UI event queue... What happens when you use CallLater() to call yourself back? ________________________________ From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Tim Sent: Wednesday, May 02, 2007 2:41 PM To: flexcoders@yahoogroups.com Subject: [flexcoders] Why aren't we allowed to process the event queue? (eg: like DoEvents) 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?
