did you just say your loading screen has a loading screen? my head just exploded
On Thu, Jul 31, 2008 at 4:54 PM, Daniel Gold <[EMAIL PROTECTED]> wrote: > My preferred "schmancy" approach is to put up a full screen loading > component that is so visually intensive that it requires it's own loading > screen that is just slightly less schmancy. Isn't recursion fun? > > On Thu, Jul 31, 2008 at 6:41 PM, Rick Winscot <[EMAIL PROTECTED]>wrote: > >> The method Daniel suggests is essentially the same that is used within >> components when enabling/disabling. When disable is called – the component >> throws up a 'blocker' that prevents interaction with the control. So... You >> could use the default component behavior of calling enabled=false (at a high >> level in the app) or do something all fancy schmancy like Daniel. I've used >> both... I just like poking fun at fellow Flexcoders and using the word >> 'schmancy.' >> >> Rick Winscot >> >> >> On 7/31/08 7:28 PM, "Daniel Gold" <[EMAIL PROTECTED]> wrote: >> >> >> >> >> Whenever I need to do this I usually put up a loading screen that covers >> the entire screen or the section of the screen pertaining to the loading >> data. This can be done a number of ways such as a full screen Popup, a modal >> popup thats just a Loading... label, etc. >> >> On Thu, Jul 31, 2008 at 5:40 PM, wwwpl <[EMAIL PROTECTED]> wrote: >> >> >> >> >> I want to block user interaction while I am waiting for an http service >> to return with data. Is there a nice easy way to do this? >> >> >> >> >> >> >> >> >> >> > >
