Because Flash is a single-threaded runtime, freezing is a bad thing, you can't interact with the app at all, and eventually you'll get an timeout error. Your users will be frustrated that they can't cancel or navigate elsewhere in your app.
When will it be ok to show those popups? You want to include that functionality in your observeValue callback. You can use callLater to have your callback called repeatedly until the criteria becomes true, but hopefully there's some other event that you can wait for instead. ________________________________ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Kevin Sent: Sunday, September 30, 2007 8:07 PM To: [email protected] Subject: Re: [flexcoders] Freeze Flex Application the main problem I am having right now is that I have some popups that get created using the ObserveValue tags. I would like to be able to prevent these popups, but the problem is that once the values come back from DataServices in the background, they are being called via the ObserveValue binding... - kevin On Sep 30, 2007, at 9:39 PM, Alex Harui wrote: Therer is no one api. What do you want to prevent? ________________________________ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Kevin Sent: Sunday, September 30, 2007 2:28 PM To: [email protected] Subject: [flexcoders] Freeze Flex Application Is there a way to freeze a flex application so that nothing can be executed both from a UI perspective and behind the scenes? I can create a modal Alert or PopUp to block user input, but I notice that code still get's executed behind the scenes and thus anything already initiated will get completed. I would like to be able halt all processes if possible. - Kevin
