Try calling validateNow after setting enabled to false.
Animations can shut down validatiom. If you can disable and re-validate before the animations start, that would be best. However, what it does, and what modal dialogs do is put up a "mouse shield" over the whole app. It's a relatively easy thing to do, and I wouldn't want to put it in CursorManager as it really doesn't have anything to do with cursors. You could have a progress bar and no busy cursor and still want to block. Maybe we need to see if we can come up with a best practice for how to use application.enabled. -Alex ________________________________ From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Bjorn Schultheiss Sent: Thursday, May 31, 2007 11:13 PM To: flexcoders@yahoogroups.com Subject: [flexcoders] Re: Disable Clicks while on busyCursor This is quite slow. I wait for the app to disable, then any animations running while the app is disabled lag. --- In flexcoders@yahoogroups.com <mailto:flexcoders%40yahoogroups.com> , "Alex Harui" <[EMAIL PROTECTED]> wrote: > > Did you try Application.application.enabled = false? > > > > ________________________________ > > From: flexcoders@yahoogroups.com <mailto:flexcoders%40yahoogroups.com> [mailto:flexcoders@yahoogroups.com <mailto:flexcoders%40yahoogroups.com> ] On > Behalf Of Troy Gilbert > Sent: Thursday, May 31, 2007 10:19 AM > To: flexcoders@yahoogroups.com <mailto:flexcoders%40yahoogroups.com> > Subject: Re: [flexcoders] Disable Clicks while on busyCursor > > > > Is it just me, or is it a bit surprising that we've got to hack > something together to handle this? Come on, Adobe... what's a proper > solution (and why wasn't it built into the CursorManager!)? I've got > enough asynchronous problems to deal with than have to worry that the > user's going to go off willy-nilly clicking buttons while the busy > cursor is being shown. I understand that some folks may not want it to > *always* prevent mouse clicks, but a little boolean flag (or two) in the > CursorManager that prevents mouse clicks and/or focus changes/keyboard > events would be very, very nice. > > Troy. > > > > On 5/31/07, Anthony Lee <[EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]> > wrote: > > >> - Make all your active components register themselves then loop > through > >> and disable/enable them according to your busy state > > > Too taxing on cpu... > > How many components are we talking about? > > Hack #3 > Generate an Alert and position it outside the viewable area. They're > modal by default... meaning the user shouldn't be able to click on > anything till you clear it. > > Anthony >
