Have you tried "this.validateNow()" ? That usually forces Flash Player to update everything on the screen -- it's kind of a "wait here 'till the screen catches up" thing...
L. On Mon, Feb 28, 2011 at 3:59 PM, Dale Bronk <[email protected]> wrote: > We had tried events as well as callLater (which I hate using). Neither > worked. > > > > *From:* [email protected] [mailto:[email protected]] *On Behalf Of *Eric > DeCoff > *Sent:* Monday, February 28, 2011 10:05 AM > *To:* [email protected] > *Subject:* Re: [AFFUG Discuss] Help with setting cursor and blocking app > please > > > > I think you logic need to be adjusted: > > > > Look into events :) > > > > > > I'll see if I can through something together > > > > > > > On Mon, Feb 28, 2011 at 12:11 PM, Dale Bronk <[email protected]> wrote: > > We're having an issue hopefully someone smarter than me can help with. We > have the following in a function (just a snippet): > > Private function onCheckboxClick() : void > { > (Application.application as MinervaApplication).mouseChildren = false; > Application.application.enabled = false; > CursorManager.setBusyCursor(); > > // Do a bunch of processing that takes a second or two where we > // want the user to be able to do anything. > // This logic does include some UI modification. > > (Application.application as MinervaApplication).mouseChildren = true; > Application.application.enabled = true; > CursorManager.removeBusyCursor(); > } > > We actually have the blocking/cursor logic abstracted out into a function, > but it is easier to show what we are doing this way. > > Our issue: > The blocking logic doesn't take affect. We do see the app "kind of freeze" > but with no visual and it just queues up the user actions. The checkbox > does not check immediately. It waits until all the logic has executed. > The > problem is that during that 1 to 2 seconds of processing the user sees the > checkbox not checked, so they check it again. That second click will queue > up so that once the initial check processing is done, it then processes the > second check creating a vicious cycle between app and user. There are a > couple places in our app where it is critical that they wait for several > calculations to be done before moving on and it seems to work just fine in > other places. Other places the cursor goes to a wait, app is disabled and > clicks are turned off so the user go click happy all they want and nothing > will happen. We have the app styled so that disabled app does not change > visually. > > Thanks, > Dale > > > > ------------------------------------------------------------- > To unsubscribe from this list, simply email the list with unsubscribe in > the subject line > > For more info, see http://www.affug.com > Archive @ http://www.mail-archive.com/discussion%40affug.com/ > List hosted by http://www.fusionlink.com > ------------------------------------------------------------- > > > > > -- > Eric R. DeCoff > Changing the world, > 1 line of code at a time > > ------------------------------------------------------------- > To unsubscribe from this list, simply email the list with unsubscribe in > the subject line > > For more info, see http://www.affug.com > Archive @ http://www.mail-archive.com/discussion%40affug.com/ > List hosted by FusionLink <http://www.fusionlink.com/> > -------------------------------------------------------------
