--- "T. R. Ponn" <[EMAIL PROTECTED]> wrote: > Jan, > > I tried it and it failed (the IDE locked up)...then > I added the obvious > (exit to top). And, just to make sure things were > back where they're > supposed to be, I added "set allowInterrupts to > true". Badda-bing! > That did it! > > Though not a biggie, I'm still struggling with > understanding the logic: > set allowInterrupts to false = allow the user to > interrupt. Sounds > backwards to me. :-D > > Thanks! > > on mouseUp > put empty into msg > set the allowInterrupts to false > repeat > if the interrupt > then cleanThisUp > else add 1 to msg > end repeat > end mouseUp > > on cleanThisUp > put "I'm interrupted" into msg > set the allowInterrupts to true > exit to top > end cleanThisUp > > > Best Regards, > > Tim Ponn > >
Hi Tim, Well you have to read it as follows: - if the allowInterrupts is true, the user can interrupt the script at any time, even in a situation that would leave data in an incorrect state. - if the allowInterrupts is false, then the user can still send the interrupt keystroke, but the developer decides when to handle the interrupt, and how to clean up and exit gracefully. Hope this clarified things a bit, Jan Schenkel. ===== "As we grow older, we grow both wiser and more foolish at the same time." (La Rochefoucauld) __________________________________ Do you Yahoo!? Protect your identity with Yahoo! Mail AddressGuard http://antispam.yahoo.com/whatsnewfree _______________________________________________ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
