Scripts that are already running

[Dar Scott]

I think this is the right immediate solution.  Jacque is always  
right.  And I have done this down deep in an I/O routine, but when I  
can, I try to embrace the event driven nature of LiveCode and avoid  
such loops.

What happens at each button click and keystroke should be fast and  
neat in the event-driven style.  These events (and others) can start  
a message engine (send recursive script) if need be.  Nothing takes a  
long time.  At each event, the state of the application might change.

(Now, given that, I think LiveCode is being cleaned up so that slave  
applications can run, and maybe we can use an alternative form of  
parallelism for some big crunching needs.)

Dar Scott



On Sep 24, 2010, at 9:31 AM, J. Landman Gay wrote:

> On 9/24/10 8:36 AM, DunbarX at aol.com wrote:
>
>> Is there a way to "interrupt", or rather, "interrogate", the  
>> repeat loop? I
>> am not talking about checking the property within that running code.
>
> I think what you want is:
>
>   wait 1 millisecond with messages
>
> Put that into the repeat loop somewhere. It forces the engine to do  
> all the same cleanup and checking as it does on idle, and will  
> catch any pending messages that have happened.
>
> -- 
> Jacqueline Landman Gay         |     jacque at hyperactivesw.com
> HyperActive Software           |     http://www.hyperactivesw.com
> _______________________________________________
> 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