Re: Endless Looping Chapter 2
In a message dated 2/3/07 3:57:24 PM, [EMAIL PROTECTED] writes: Hi Everyone Is there a way for me to stop a running script that’s caught in an endless loop so I can fix my scripting error? Joe Orlando, Florida I tried “AllowInterrupts” it didn’t allow me to break in, even when I put it into the offending handler. The other suggestions assume I know in advance which handler will cause a problem. Is there a universal solution I can apply at startup to allow me to break a script? Joe Orlando, Florida ___ 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
Re: Endless Looping Chapter 2
Joe, allowInterrupts is a global (and persistent, I think) property of the IDE (which defaults to true, in 2.7.4 at least). As long is it is set to true you should be able to interrupt a runaway loop by holding command - period (Mac) or control - period (Windows). There was a version (2.7.2?) which wrongly defaulted to false, and before I realised what was going on, I just got into the habit of putting if the controlKey is down then exit repeat inside every loop, until I was sure the loop was ok. The cmnd/cntrl period should work, though. Best, Mark On 4 Feb 2007, at 04:22, [EMAIL PROTECTED] wrote: In a message dated 2/3/07 3:57:24 PM, [EMAIL PROTECTED] writes: Hi Everyone Is there a way for me to stop a running script that’s caught in an endless loop so I can fix my scripting error? Joe Orlando, Florida I tried “AllowInterrupts” it didn’t allow me to break in, even when I put it into the offending handler. The other suggestions assume I know in advance which handler will cause a problem. Is there a universal solution I can apply at startup to allow me to break a script? Joe Orlando, Florida ___ 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
Re: Endless Looping Chapter 2
Hi Joe, Short of universal execution controllers (which I'm not aware of), I would recommend you do something like this: First, identify where the problem is. - comment out most of your code, just leaving some very basic stuff. - save. - run a test. - uncomment a little code. - save. - do another test. - repeat this cycle until you get a failure. When you finally get a failure, you'll know it's associated with the code you most recently uncommented. Second, use one of the methods you now know from previous posts to interrupt the endless loop when it happens. HTH - Phil Davis [EMAIL PROTECTED] wrote: In a message dated 2/3/07 3:57:24 PM, [EMAIL PROTECTED] writes: Hi Everyone Is there a way for me to stop a running script that’s caught in an endless loop so I can fix my scripting error? Joe Orlando, Florida I tried “AllowInterrupts” it didn’t allow me to break in, even when I put it into the offending handler. The other suggestions assume I know in advance which handler will cause a problem. Is there a universal solution I can apply at startup to allow me to break a script? Joe Orlando, Florida ___ 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
Re: Endless Looping Chapter 2
[EMAIL PROTECTED] wrote: I tried “AllowInterrupts” it didn’t allow me to break in, even when I put it into the offending handler. It's a global property, you set it once and forget about it. Put this into the message box: set the allowinterrupts to true After that, command-period should allow you to break into any script and stop it. The property will be persisitent for the entire session. If you are using the latest release of 2.7.4, then the allowInterrupts should be set to true automatically by the IDE, and doing the above won't change anything. But if you are using the last release before this one, it shipped with this property set to false and command-period didn't work. Setting it in the message box will fix it. -- Jacqueline Landman Gay | [EMAIL PROTECTED] HyperActive Software | http://www.hyperactivesw.com ___ 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
