The waitDepth tells you how many nested wait calls are (recursively) in progress - that might be useful for what you need.
Warmest regards, Mark. Sent from my iPhone > On 27 Nov 2016, at 14:08, Mike Kerner <mikeker...@roadrunner.com> wrote: > > If a beginner was asking this question, I would skip the thread and move on > because...come on. LC is single-threaded. > > HOWEVER, wait with messages brings up an interesting problem - how to tell > if a script that was waiting...with messages is waiting, or is dead, > perhaps exited. I don't really want to do the compile/launch workaround, > because I want to be able to have Bad Things trip the debugger, which is > hard to do with standalones. > > I suppose I could have the script update a global each time it begins a > wait, and then have the cron script look for that, and if we're past a > certain time, assume that the wait is over, but that assumes I don't > introduce some error, later and forget to update the variable. > > -- > On the first day, God created the heavens and the Earth > On the second day, God created the oceans. > On the third day, God put the animals on hold for a few hours, > and did a little diving. > And God said, "This is good." > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
