> happening all the time. Is there a way to switch the 'blurring' off? >
if you want to play with the amount of blurring in the background for a modal popup, you have to set 'modalTransparencyBlur' style eg <mx:Applictaion modalTransparencyBlur="0"> (default is 3) --- In flexcoders@yahoogroups.com, "Franck de Bruijn" <[EMAIL PROTECTED]> wrote: > > Asynchronous event driven architecture are a nice thing, however In a GUI > you sometimes just *have* to wait before things come back, otherwise your > system becomes instable. > > > > For example, let's say I'm doing an expensive search (takes a couple of > seconds). The result needs to be placed into a datagrid or something like > that. If I can close the window in which the datagrid is hosted within the > 'waiting' period, the datagrid will be gone. Once the result of the search > comes back it will not find the datagrid anymore, and highly likely an error > will be the result. > > > > I used the TitleWindow approach myself, but I did not like the 'blurring' > happening all the time. Is there a way to switch the 'blurring' off? > > > > Cheers, > > Franck > > > > _____ > > From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On > Behalf Of Paul Andrews > Sent: Tuesday, August 01, 2006 5:07 AM > To: flexcoders@yahoogroups.com > Subject: Re: [flexcoders] Re: Simple way to do "Please wait..." type window > > > > ----- Original Message ----- > From: "JesterXL" <[EMAIL PROTECTED] <mailto:jesterxl% 40jessewarden.com> > n.com> > To: <[EMAIL PROTECTED] <mailto:flexcoders%40yahoogroups.com> ups.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. > <http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt> > yahoo.com/group/flexcoders/files/flexcodersFAQ.txt > > Search Archives: http://www.mail- > <http://www.mail-archive.com/flexcoders%40yahoogroups.com> > 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/
