Progress Indicator Revisited

Bob Sneidar bobs at twft.com
Thu Mar 24 13:35:10 EDT 2011


That worked a peach. Thanks. Since I am only updating my SQL tables when something has changed I can optimize my speed by putting the wait command right after the code that actually writes to the SQL database. 

Bob


On Mar 24, 2011, at 9:47 AM, Scott Rossi wrote:

> Recently, Bob Sneidar wrote:
> 
>> I know this has been hashed out before, but what did we decide? I am going
>> through 3 nested loops, each of which puts some text into a field to indicate
>> how far along in the process I am. Trouble is, nothing shows up in the field
>> until everything is done.
>> 
>> Is there a way to force the screen to refresh in a loop so I can see a
>> progress indicator? I tried to send idle in 0 seconds each time I went through
>> the loop, but no joy.
> 
> If I understand what you're asking, this can only work if your "process" can
> accommodate a wait or pause while it's operating.  Some folks use a "wait x
> millisecs with messages" in a repeat loop (even a value of zero will work in
> some cases).  Another way is to use "send in" instead of a repeat loop which
> inherently has "breaks" built in between cycles.  But each of these depend a
> bit on what your process is doing and how it's doing it.
> 
> Regards,
> 
> Scott Rossi
> Creative Director
> Tactile Media, UX Design
> 
> 
> 
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode





More information about the Use-livecode mailing list