Display progress

Sarah sarahr at genesearch.com.au
Sun Dec 15 17:23:01 EST 2002

One thing to keep in mind is that constant progress updating can slow 
down your processing. If you use a progress bar or the busy cursor, 
don't update every time through your loop, but limit it to ever 10th, 
100th or whatever makes sense.

As an alternative suggestion, can you do this processing as the 
application starts up? People are quite accustomed to being kept 
waiting at the splash screen especially if you have a text message and 
busy cursor showing that something is really happening. Then once the 
program starts, you can go directly to the card without delay.


On Sunday, December 15, 2002, at 04:15  am, Barry Levine wrote:

> I have an app that has some processing to do when it reaches a certain 
> card. I have the handler in the openCard script. This can take 
> anywhere from four to eight seconds depending on the speed of the 
> computer. I'd like to display a small progess indicator - even 
> something as simple as a window that tells the user to be patient for 
> a few more seconds. I don't even need to provide a thermometer or a 
> counter.
> I thought about displaying a modal window but the docs say that doing 
> so will bring all processing to a halt so that's obviously not the 
> answer. I don't want the user to be able to click in the "main" window 
> until the app is ready, however. This is probably four lines of code, 
> right? Any help would be appreciated.
> Thanks,
> Barry
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> http://lists.runrev.com/mailman/listinfo/use-revolution

More information about the Use-livecode mailing list