look in the archives of posts from last two weeks, where this was discussed fairly well. link to archives http://www.mail-archive.com/use-revolution@lists.runrev.com/
Basically--------------- Rule 1 make sure the "user can't abort scripts" is false (un-checked) if the optionkey is down then breakpoint if the optionkey is down then exit to top if the optionkey is down then exit repeat put the seconds into noww repeat forever if the seconds - noww > (24*60*60) then it is tomorrow end repeat put 0 into cntr repeat forever add 1 to cntr if cntr > 43562121 then breakpoint end repeat Just a few ways Jim Ault Las Vegas On 7/2/06 10:36 PM, "Terry Vogelaar" <[EMAIL PROTECTED]> wrote: > Hi all, > > I have a script that somehow has an infinite loop somewhere, although > I cannot see where or why. > > Back in the HyperCard days I ran more often into such an error. I had > to use Command-dot often to stop executing scripts. But RunRev 2.7 > doesn't seem to respond to that. So I force-quit RunRev. But is there > another way to abort executing scripts? > > Also, is there a way to give a handler a maximum time to finish? > > Terry > _______________________________________________ > use-revolution mailing list > use-revolution@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-revolution _______________________________________________ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
