Depends. The spinning watch is what we use 100% of the time; that's the
default cursor that still allows you to click around. However, for some
interfaces where you DON'T want the user to click anything and need to force
them to wait, modality works great; it's why they gave us modality, for
those use cases.
Besides, it's 1 line of code:
WaitWindow.showProgress("Loading...", false);
Both Flex 1.5 & Flex 2 have their PopUpManager's createPopUp method default
to false for modality. Flex 1.5 actually came with a cursor you could use
that was the cursor + hourglass. I always wished they made that the default
cursor because the majority of the time, most of the HTTPService /
RemoteObject calls were quick one shots that still allowed the user to click
around, and this a cursor was an appropriate thing to show.
----- Original Message -----
From: "Paul Andrews" <[EMAIL PROTECTED]>
To: <flexcoders@yahoogroups.com>
Sent: Monday, July 31, 2006 11:06 PM
Subject: Re: [flexcoders] Re: Simple way to do "Please wait..." type window
----- Original Message -----
From: "JesterXL" <[EMAIL PROTECTED]>
To: <flexcoders@yahoogroups.com>
Sent: Tuesday, August 01, 2006 2:26 AM
Subject: Re: [flexcoders] Re: Simple way to do "Please wait..." type window
> One way I did it was making a Singleton class that popups up a small
> TitleWindow. This TitleWindow has a ProgressBar in it. The ProgressBar's
> indeterminate is bound to the visibility (you don't want it playing while
> the window is invisible; takes up resources). You can then do:
>
> WaitWindow.showProgress("Loading...");
>
> Inside, it'll create a popup if none exists, and put the text in there.
> It's modal by default. You can then later go:
>
> WaitWindow.remove();
>
> And if one exists, it'll remove it. Subsequent calls to showProgress
> merely
> update the text. You can use this for changed commands.
Are modal windows really a good way to go with this? It seems to me to be a
step backward when you are stopping the user from doing anything whilst data
is loading. What happens if the load is particularly slow, fails, or was
accidentally initiated and the user changes their mind?
Seems to me that modal progress windows just go completely against the idea
of an asynchronous event driven architecture.
Paul
> --
> Flexcoders Mailing List
> FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
> Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com
> Yahoo! Groups Links
>
>
>
>
>
>
>
>
--
Flexcoders Mailing List
FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com
Yahoo! Groups Links
--
Flexcoders Mailing List
FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/flexcoders/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
