Repeat Loops Blocking Handlers-Screen Update?

[Jan Schenkel]

Try putting 'wait 0 seconds' before and/or inside your loop. This usually gives the engine enough 'breathing room' to redraw the screen.

Jan Schenkel
=====
Quartam Reports & PDF Library for Revolution
<http://www.quartam.com>

=====
"As we grow older, we grow both wiser and more foolish at the same time."  (La Rochefoucauld)


--- On Tue, 7/21/09, Sivakatirswami <katir at hindu.org> wrote:

> From: Sivakatirswami <katir at hindu.org>
> Subject: Repeat Loops Blocking Handlers-Screen Update?
> To: "How to use Revolution" <use-revolution at lists.runrev.com>
> Date: Tuesday, July 21, 2009, 5:23 PM
> I have what I think is a new
> phenomenon in 3.5... I could have sworn this was not a
> problem in previous versions, correct me if I'm wrong
> 
> I like to use a small field on the interface to provide low
> noise feedback to the user rather than throwing up a big
> striking modal dialog.
> 
> I'll typically have a small feedback field on the UI and
> then have this in the stackscript
> 
> on showFeedback tMsg
>   put tMsg into fld "FeedbackMsg"
>   show fld "FeedbackMsg"
>   send  hideFeedback to me in 10 seconds
> end showFeedback
> on hideFeedback
>   hide fld "feedbackmsg"
> put empty into "feedbackmsg"
> end hideFeedback
> 
> Now... I have an application that mounts our server over
> the LAN, using Apples script, then from a button I issue a
> call to the stack script to get a collection. the script
> proceeds to set default directories and do some pretty
> intense directory walking then load a file list in the uswer
> interface. Basically this is a flat file based run-time
> update index to audio collections on the server.  This
> all works amazingly well, except that my button issues the
> feedback-status update before issuing the directory walker
> commands, the interface never responds.. My message field is
> never shown.   I've tested from the msg box
> and sending "showfeedback ("Loading...") works fine...
> nothing wrong with the scripts... something is blocking the
> screen refresh update, even though I issue that cmd *before*
> the big dig repeat loops to get file lists from the
> server...
> 
> Any clues?
> 
> Also the cmd to empty the index field is not executed if I
> put the handlers into that stack command
> 
> command LoadCollection pCollection
>      showFeedback
> ("Loading...")   # this and the next cmd are
> executed, but
>      put "" into fld
> "currentindex"  # we never see it on  screen until
> the following are done:
>     clearGlobals
>   digFiles pCollection
>   LoadIndexArray
> end LoadCollection
> 
> IN the above...I never actually see the fld "CurrentIndex"
> go blank and the feedback field showing "Loading..."
> on  appears after all the repeat loops have done their
> job.
> 
> 
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage
> your subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-revolution
>