Re: How do I abort a handler in OS X???

[Richard Gaskin]

J. Landman Gay jacque wrote:
Did another test and guess what -- allowInterrupts was set to false. 
When it is changed to true, Command-period does work. So whatever is 
setting the default value of allowInterrupts is consistent; possibly its 
in the engine?


Bug in v2.7.x:


--
 Richard Gaskin
 Managing Editor, revJournal
 ___
 Rev tips, tutorials and more: http://www.revJournal.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

Re: How do I abort a handler in OS X???

[J. Landman Gay]

Ben Rubinstein wrote:

On 27/6/06 18:15, J. Landman Gay wrote:

J. Landman Gay wrote:

Ben Rubinstein wrote:

Minor update: this bug is still present in 2.7.2; it applies even after
'suspend development environment'; but it doesn't apply to 
standalones built
with 2.7.2, ie cmd-period interrupts fine.  So it's not in the 2.7.2 
engine,

it's something in the 2.7.x IDE - and something that isn't suspended.


Good sleuthing. I didn't realize it was an IDE thing. That should be 
much easier to fix than an engine bug.  Thanks for reporting it.




I sort of take this back. I just tried it in the MC IDE and it also 
fails there.


Interesting - I guess that's in some sense consistent with the fact that 
the problem is still present after "Suspend Development Tools".  Do you 
confirm (in case I'm mad) that interrupt is still working in standalones?


Perhaps you could also add your MC findings to BZ 3713.


Did another test and guess what -- allowInterrupts was set to false. 
When it is changed to true, Command-period does work. So whatever is 
setting the default value of allowInterrupts is consistent; possibly its 
in the engine?


--
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

Re: [FIX] How do I abort a handler in OS X???

[Ben Rubinstein]

On 27/6/06 19:47, Peter T. Evensen wrote:
It appears to default to false in the IDE of 2.7.2  It seems like it 
should be true.


At 01:42 PM 6/27/2006, you wrote:

The problem is fixed with:

set the allowinterrupts to true

This should be the default at startup but I found it was set to false
in the current version.


Excellent catch, Peter - thank you.  I had checked for the cantAbort of the 
stack, but not the global allowInterrupts.


I've added this info to BZ.

  Ben Rubinstein   |  Email: [EMAIL PROTECTED]
  Cognitive Applications Ltd   |  Phone: +44 (0)1273-821600
  http://www.cogapp.com|  Fax  : +44 (0)1273-728866

___
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: [FIX] How do I abort a handler in OS X???

[Peter T. Evensen]

It appears to default to false in the IDE of 2.7.2  It seems like it should 
be true.


At 01:42 PM 6/27/2006, you wrote:

The problem is fixed with:

set the allowinterrupts to true

This should be the default at startup but I found it was set to false
in the current version.


Peter T. Evensen
http://www.PetersRoadToHealth.com
314-629-5248 or 888-682-4588 



___
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: [FIX] How do I abort a handler in OS X???

[iMed Edition]

The problem is fixed with:

set the allowinterrupts to true

This should be the default at startup but I found it was set to false  
in the current version.



___
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: How do I abort a handler in OS X???

[Ben Rubinstein]

On 27/6/06 18:15, J. Landman Gay wrote:

J. Landman Gay wrote:

Ben Rubinstein wrote:

Minor update: this bug is still present in 2.7.2; it applies even after
'suspend development environment'; but it doesn't apply to 
standalones built
with 2.7.2, ie cmd-period interrupts fine.  So it's not in the 2.7.2 
engine,

it's something in the 2.7.x IDE - and something that isn't suspended.


Good sleuthing. I didn't realize it was an IDE thing. That should be 
much easier to fix than an engine bug.  Thanks for reporting it.




I sort of take this back. I just tried it in the MC IDE and it also 
fails there.


Interesting - I guess that's in some sense consistent with the fact that the 
problem is still present after "Suspend Development Tools".  Do you confirm 
(in case I'm mad) that interrupt is still working in standalones?


Perhaps you could also add your MC findings to BZ 3713.

  Ben Rubinstein   |  Email: [EMAIL PROTECTED]
  Cognitive Applications Ltd   |  Phone: +44 (0)1273-821600
  http://www.cogapp.com|  Fax  : +44 (0)1273-728866

___
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: How do I abort a handler in OS X???

[J. Landman Gay]

J. Landman Gay wrote:

Ben Rubinstein wrote:

On 27/6/06 16:39, Ben Rubinstein wrote:
So this is a bug introduced in some version of 2.7 - does this 
represent a touching confidence by RunRev that their user-programmers 
are now so sophisticated that they'll never make mistakes anymore, 
sort of like Steve Jobs removing the reset switch on Macs?  Feels 
like another reason for me to stick on 2.6.1, since I know just how 
not-sophisticated *I* am!


Minor update: this bug is still present in 2.7.2; it applies even after
'suspend development environment'; but it doesn't apply to standalones 
built
with 2.7.2, ie cmd-period interrupts fine.  So it's not in the 2.7.2 
engine,

it's something in the 2.7.x IDE - and something that isn't suspended.


Good sleuthing. I didn't realize it was an IDE thing. That should be 
much easier to fix than an engine bug.  Thanks for reporting it.




I sort of take this back. I just tried it in the MC IDE and it also 
fails there.


--
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

Re: How do I abort a handler in OS X???

[Jeffrey Reynolds]

Jim,

actually use my own flag since i sometimes leave debugging stuff  
turned on in the standalone when wanting to track things in the  
standalone or kill loops problems when they show up there. also  
sometimes want these turned off when in the development environment  
for testing before moving to a standalone. its useful to be in  
control of this flag. usually have a toggle button for it on the main  
card until near the end of development to allow these functions to be  
turned on and off until near the end of development.


cheers,

jeff

Jeffrey Reynolds



On Jun 27, 2006, at 5:54 AM, [EMAIL PROTECTED]  
wrote:



you could also use the built-in
if the environment is "development" then showDevelopOptions


hate stripping code when i am already through part of testing to easy
to screw something up that was working perfectly well and then theres
usually that one gotcha later in testing that its nice to have your
early debugging stuff still there and available for use in figuring
out what is going wrong... I also use it to pass results repeat end
numbers and other variables into a displayable field so i can easily
watch what is going on in more complex scripts that need tweaking.
again only displayed if the field is show and the development mode
variable is set right.


___
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: How do I abort a handler in OS X???

[J. Landman Gay]

Ben Rubinstein wrote:

On 27/6/06 16:39, Ben Rubinstein wrote:
So this is a bug introduced in some version of 2.7 - does this 
represent a touching confidence by RunRev that their user-programmers 
are now so sophisticated that they'll never make mistakes anymore, 
sort of like Steve Jobs removing the reset switch on Macs?  Feels like 
another reason for me to stick on 2.6.1, since I know just how 
not-sophisticated *I* am!


Minor update: this bug is still present in 2.7.2; it applies even after
'suspend development environment'; but it doesn't apply to standalones 
built
with 2.7.2, ie cmd-period interrupts fine.  So it's not in the 2.7.2 
engine,

it's something in the 2.7.x IDE - and something that isn't suspended.


Good sleuthing. I didn't realize it was an IDE thing. That should be 
much easier to fix than an engine bug.  Thanks for reporting 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

Re: How do I abort a handler in OS X???

[Ben Rubinstein]

On 27/6/06 16:39, Ben Rubinstein wrote:
So this is a bug introduced in some version of 2.7 - does this represent 
a touching confidence by RunRev that their user-programmers are now so 
sophisticated that they'll never make mistakes anymore, sort of like 
Steve Jobs removing the reset switch on Macs?  Feels like another reason 
for me to stick on 2.6.1, since I know just how not-sophisticated *I* am!


Minor update: this bug is still present in 2.7.2; it applies even after
'suspend development environment'; but it doesn't apply to standalones built
with 2.7.2, ie cmd-period interrupts fine.  So it's not in the 2.7.2 engine,
it's something in the 2.7.x IDE - and something that isn't suspended.

I've added this to Bugzilla as #3713.

  Ben Rubinstein   |  Email: [EMAIL PROTECTED]
  Cognitive Applications Ltd   |  Phone: +44 (0)1273-821600
  http://www.cogapp.com|  Fax  : +44 (0)1273-728866


___
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: How do I abort a handler in OS X???

[Ben Rubinstein]

On 27/6/06 16:27, J. Landman Gay wrote:

Ben Rubinstein wrote:

I don't think there's any problem with cmd-period in OS-X; but there 
is, and always has been, a problem that cmd-period doesn't work if 
you've got a modal dialog in the way.


Very true, but I think there's a problem with Command-period inside any 
repeat loop as well, regardless of whether it displays a modal or not.


Try this:

on test
 put 0 into tNum
 repeat
  if the shiftkey is down then exit repeat
  add 1 to tNum
  put tNum
 end repeat
end test

Issue "test" from the message box. Now try to Command-period out of it. 
If the shiftkey bypass wasn't in there, you'd have to force-quit.


Huh?  Ooer... 2.7 bug.   I tried your test in 2.6.1 (currently still my 
"production" system) and in 2.5.1, because I happened to have it open as well 
- cmmd-period interrupted fine in both cases.


Then I launched the 2.7.1 that I have for gingerly dipping my toe into - and I 
see your point!  I'm just trying to update it to 2.7.2 (though it's a shame to 
lose the 2.x.1 rhythm) - but I assume that a modern person such as yourself is 
using that already.


So this is a bug introduced in some version of 2.7 - does this represent a 
touching confidence by RunRev that their user-programmers are now so 
sophisticated that they'll never make mistakes anymore, sort of like Steve 
Jobs removing the reset switch on Macs?  Feels like another reason for me to 
stick on 2.6.1, since I know just how not-sophisticated *I* am!


  Ben Rubinstein   |  Email: [EMAIL PROTECTED]
  Cognitive Applications Ltd   |  Phone: +44 (0)1273-821600
  http://www.cogapp.com|  Fax  : +44 (0)1273-728866

___
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: How do I abort a handler in OS X???

[J. Landman Gay]

Ben Rubinstein wrote:

I don't think there's any problem with cmd-period in OS-X; but there is, 
and always has been, a problem that cmd-period doesn't work if you've 
got a modal dialog in the way.


Very true, but I think there's a problem with Command-period inside any 
repeat loop as well, regardless of whether it displays a modal or not.


Try this:

on test
 put 0 into tNum
 repeat
  if the shiftkey is down then exit repeat
  add 1 to tNum
  put tNum
 end repeat
end test

Issue "test" from the message box. Now try to Command-period out of it. 
If the shiftkey bypass wasn't in there, you'd have to force-quit.


--
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

Re: How do I abort a handler in OS X???

[Stephen Barncard]

interestingCMD-PERIOD never worked in Rev for me... ever.

sqb



So much for deep background.  No doubt you've force-quit by now 
anyway.  But for future use:


a) cmd-period works in general just as well in OS-9 as in OS-X.  But 
there's no way to abort a script when an answer dialog is showing, 
unless you coded for the possibility (ie 'answer xxx with "Stop" or 
"Continue"/if it = "Stop" then exit to top).


--
stephen barncard
s a n  f r a n c i s c o
- - -  - - - - - - - - -
___
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: How do I abort a handler in OS X???

[Bill Marriott]

FYI... I found that while Command (or Control) - period doesn't work, 
Command-S will often save the stack. That takes a bit of the pain out of the 
force-quit. 



___
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: How do I abort a handler in OS X???

[Jim Carwardine]

An amazingly detailed answer... I did try and beat the loop by clicking ok
and then hitting cmd/period.  Couldn't beat it.  I like your suggestions for
remedies.  I will implement them but, at the same time, I'll put in the on
shiftKey trapdoor as well... Jim

on 6/27/06 6:48 AM, Ben Rubinstein wrote:

> On 26/6/06 22:05, Jim Carwardine wrote:
>> Yes, that's my problem... Cmd-period didn't work... And there appears to be
>> no substitution remedy.  I was developing a script and wanted to test a
>> piece of logic inside a repeat loop so I put in an answer variable line as I
>> always do.  Then I got an answer dialogue with each iteration of about 1500
>> iterations which was impossible when I couldn't abort the handler.  BTW
>> cmd/s doesn't work either... Jim
> 
> Hi Jim,
> 
> I don't think there's any problem with cmd-period in OS-X; but there is, and
> always has been, a problem that cmd-period doesn't work if you've got a modal
> dialog in the way.
> 
> The problem is that the modal dialog (which of course in Rev is really another
> stack, with its own event loop) exists in another thread or "execution layer"
> (I don't know technically how its implemented, I'm just trying to express how
> it behaves.)  So cmd-period works perfectly well as an interrupt; but if the
> answer dialog is up, you're just interrupting that, and since it wasn't doing
> anything anyway, nothing happens.   Then you click OK, and you're back in the
> stuck loop.  If you were really, unfeasibly, quick, you could click OK and
> then type cmd-period to the underlying stack before it throws up the next
> answer dialog, and then you'd stop it OK.  But typically in this situation,
> Rev is too fast for you.
> 
> This applies as much to Windows and OS 9 as OS X; however, you do have a
> couple more chances saving your data on the Mac, see below.
> 
> I've got into this situation many times, typically I have some data-processing
> loop, and I think that I'd like to know if some situation that should never
> occur does so.  So I put in a "just in case" alert, click the button - and
> then it turns out that due either to my misunderstanding, or erroneous coding,
> the test fires on every one of 10,000 lines.
> 
> If I remember, I put in a 'hold down shift' emergency exit to escape from
> loops like this.  Increasingly, I've tried to train myself to put in
> breakpoint for that situation, instead of or just after the "answer" call.
> But of course from time to time I forget and get bit again.
> 
> Once when I was working on a shell that was to host a variety of data
> processing scripts, I took a copy of the Rev answer stack, and modified it to
> include a button that would do "exit to top" as a kind of emergency stop
> button.  It's so cool that in Rev you can do this... but unfortunately, it
> didn't solve it.  Just like cmd-period, "exit to top" when executed from
> inside the modal dialog affected only that 'layer'.  There seend as far as I
> could tell to be no way to really halt the underlying script; it's suspended
> when the modal dialog is invoked; but regardless of what happens while the
> modal dialog is open, once closed the underlying script is resumed.
> 
> I set off a correspondence on the improve list, wait, let me see... just over
> four years ago!... on exactly this topic, but we never found a good solution.
> Unfortunately, this was before Bugzilla had been opened to the users, and so
> nothing was entered anywhere persistent that might help.
> 
> So much for deep background.  No doubt you've force-quit by now anyway.  But
> for future use:
> 
> a) cmd-period works in general just as well in OS-9 as in OS-X.  But there's
> no way to abort a script when an answer dialog is showing, unless you coded
> for the possibility (ie 'answer xxx with "Stop" or "Continue"/if it = "Stop"
> then exit to top).
> 
> b) I keep an applescript file handy called "Rev Saviours".  It has a variety
> of useful expressions in it which I uncomment and try when I'm in a situation
> like this.
> 
> The one that helps here looks like this:
> 
>   tell application "Revolution"
>  do script "close stack \"Answer Dialog\" ; save topStack()"
>   end tell
> 
> You'll still be stuck in your loop - but your stack has been saved, so as long
> as you weren't worried about data in variables, you can force-quit with an
> easy heart.
> 
> 
> c) If you do have to resort to force-quit, make sure that you can see your
> stack when you do it.  In some situations on OS X, when Rev is force-quit it
> briefly offers to save your stack - if you immediately click the button, it
> really does do so.
> 
>  Ben Rubinstein   |  Email: [EMAIL PROTECTED]
>  Cognitive Applications Ltd   |  Phone: +44 (0)1273-821600
>  http://www.cogapp.com|  Fax  : +44 (0)1273-728866
> 
> ___
> use-revolution mailing list
> use-revolution@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscr

Re: How do I abort a handler in OS X???

[Jim Carwardine]

Yes, I did force quit.  I guess the confusion was that cmd/period does work
if you are not in a repeat loop because I just naturally use it if I need
to... Jim

on 6/26/06 6:00 PM, J. Landman Gay wrote:

> Jim Carwardine wrote:
>> Hi Folks... I've just upgraded to Rev 2.7.2 in OS X and can't seem to get
>> command/period to abort a handler in an infinite repeat loop.  It that only
>> a Classic function?  How do I do it in OS X?  I can't look it up in the rev
>> docs because my IDE is busy inside my repeat loop which I can't abort.  I'd
>> like to be able to save the script changes so I don't want to force quit.
>> 
>> How do I abort a handler?  Jim
> 
> You've probably already force-quit by now, but just for the record, you
> can't get out of one of these and force-quitting is about all you can
> do. This has hit me many times, and now I am (almost) in the habit of
> inserting a line like this into every new repeat loop I write:
> 
>  if the shiftkey is down then exit repeat
> 
> Once I know the thing works okay, I generally take the line out. But it
> has saved me multiple times.
> 
> For some reason, Command-period can't break into a repeat loop. I think
> the engine runs those as fast as it can without checking the keyboard
> input. You might want to Bugzilla this, because it happens a lot.

-- 

www.TalentSeeker.ca   www.HiringSmart.ca/ns   www.KeepingTheBest.ca/ns


Own Your Future Consulting Services Limited,
23 Shoal Cove Road, Seabright, Nova Scotia, Canada.  B3Z 3A9
Phone: 902-823-2339. Fax: 902-823-2139




___
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: How do I abort a handler in OS X???

[Ben Rubinstein]

On 26/6/06 22:05, Jim Carwardine wrote:
> Yes, that's my problem... Cmd-period didn't work... And there appears to be
> no substitution remedy.  I was developing a script and wanted to test a
> piece of logic inside a repeat loop so I put in an answer variable line as I
> always do.  Then I got an answer dialogue with each iteration of about 1500
> iterations which was impossible when I couldn't abort the handler.  BTW
> cmd/s doesn't work either... Jim

Hi Jim,

I don't think there's any problem with cmd-period in OS-X; but there is, and 
always has been, a problem that cmd-period doesn't work if you've got a modal 
dialog in the way.


The problem is that the modal dialog (which of course in Rev is really another 
stack, with its own event loop) exists in another thread or "execution layer" 
(I don't know technically how its implemented, I'm just trying to express how 
it behaves.)  So cmd-period works perfectly well as an interrupt; but if the 
answer dialog is up, you're just interrupting that, and since it wasn't doing 
anything anyway, nothing happens.   Then you click OK, and you're back in the 
stuck loop.  If you were really, unfeasibly, quick, you could click OK and 
then type cmd-period to the underlying stack before it throws up the next 
answer dialog, and then you'd stop it OK.  But typically in this situation, 
Rev is too fast for you.


This applies as much to Windows and OS 9 as OS X; however, you do have a 
couple more chances saving your data on the Mac, see below.


I've got into this situation many times, typically I have some data-processing 
loop, and I think that I'd like to know if some situation that should never 
occur does so.  So I put in a "just in case" alert, click the button - and 
then it turns out that due either to my misunderstanding, or erroneous coding, 
the test fires on every one of 10,000 lines.


If I remember, I put in a 'hold down shift' emergency exit to escape from 
loops like this.  Increasingly, I've tried to train myself to put in 
breakpoint for that situation, instead of or just after the "answer" call. 
But of course from time to time I forget and get bit again.


Once when I was working on a shell that was to host a variety of data 
processing scripts, I took a copy of the Rev answer stack, and modified it to 
include a button that would do "exit to top" as a kind of emergency stop 
button.  It's so cool that in Rev you can do this... but unfortunately, it 
didn't solve it.  Just like cmd-period, "exit to top" when executed from 
inside the modal dialog affected only that 'layer'.  There seend as far as I 
could tell to be no way to really halt the underlying script; it's suspended 
when the modal dialog is invoked; but regardless of what happens while the 
modal dialog is open, once closed the underlying script is resumed.


I set off a correspondence on the improve list, wait, let me see... just over 
four years ago!... on exactly this topic, but we never found a good solution. 
 Unfortunately, this was before Bugzilla had been opened to the users, and so 
nothing was entered anywhere persistent that might help.


So much for deep background.  No doubt you've force-quit by now anyway.  But 
for future use:


a) cmd-period works in general just as well in OS-9 as in OS-X.  But there's 
no way to abort a script when an answer dialog is showing, unless you coded 
for the possibility (ie 'answer xxx with "Stop" or "Continue"/if it = "Stop" 
then exit to top).


b) I keep an applescript file handy called "Rev Saviours".  It has a variety 
of useful expressions in it which I uncomment and try when I'm in a situation 
like this.


The one that helps here looks like this:

   tell application "Revolution"
  do script "close stack \"Answer Dialog\" ; save topStack()"
   end tell

You'll still be stuck in your loop - but your stack has been saved, so as long 
as you weren't worried about data in variables, you can force-quit with an 
easy heart.



c) If you do have to resort to force-quit, make sure that you can see your 
stack when you do it.  In some situations on OS X, when Rev is force-quit it 
briefly offers to save your stack - if you immediately click the button, it 
really does do so.


  Ben Rubinstein   |  Email: [EMAIL PROTECTED]
  Cognitive Applications Ltd   |  Phone: +44 (0)1273-821600
  http://www.cogapp.com|  Fax  : +44 (0)1273-728866

___
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: How do I abort a handler in OS X???

[Jim Carwardine]

Yes, that's my problem... Cmd-period didn't work... And there appears to be
no substitution remedy.  I was developing a script and wanted to test a
piece of logic inside a repeat loop so I put in an answer variable line as I
always do.  Then I got an answer dialogue with each iteration of about 1500
iterations which was impossible when I couldn't abort the handler.  BTW
cmd/s doesn't work either... Jim

on 6/26/06 4:59 PM, Mark Smith wrote:

> Sadly, cmd-period doesn't seem to do it. I'm on OS X.
> 
> I've adopted the habit of putting "if the optionKey is dwon then exit
> to top" at the start of the loop until I've debugged it enough to be
> sure it isn't going to be infinite...which is no help at all in your
> current predicament. You could try cmd-S before you force quit. I
> seem to remember that it actually worked one time, but I could be wrong.
> 
> Best,
> 
> Mark
> 
> 
> On 26 Jun 2006, at 20:22, Jim Carwardine wrote:
> 
>> Hi Folks... I've just upgraded to Rev 2.7.2 in OS X and can't seem
>> to get
>> command/period to abort a handler in an infinite repeat loop.  It
>> that only
>> a Classic function?  How do I do it in OS X?  I can't look it up in
>> the rev
>> docs because my IDE is busy inside my repeat loop which I can't
>> abort.  I'd
>> like to be able to save the script changes so I don't want to force
>> quit.
>> 
>> How do I abort a handler?  Jim
>> -- 
>> 
>> 
>> 
>> ___
>> 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

-- 

www.TalentSeeker.ca   www.HiringSmart.ca/ns   www.KeepingTheBest.ca/ns


Own Your Future Consulting Services Limited,
23 Shoal Cove Road, Seabright, Nova Scotia, Canada.  B3Z 3A9
Phone: 902-823-2339. Fax: 902-823-2139




___
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: How do I abort a handler in OS X???

[J. Landman Gay]

Jim Carwardine wrote:

Hi Folks... I've just upgraded to Rev 2.7.2 in OS X and can't seem to get
command/period to abort a handler in an infinite repeat loop.  It that only
a Classic function?  How do I do it in OS X?  I can't look it up in the rev
docs because my IDE is busy inside my repeat loop which I can't abort.  I'd
like to be able to save the script changes so I don't want to force quit.

How do I abort a handler?  Jim


You've probably already force-quit by now, but just for the record, you 
can't get out of one of these and force-quitting is about all you can 
do. This has hit me many times, and now I am (almost) in the habit of 
inserting a line like this into every new repeat loop I write:


  if the shiftkey is down then exit repeat

Once I know the thing works okay, I generally take the line out. But it 
has saved me multiple times.


For some reason, Command-period can't break into a repeat loop. I think 
the engine runs those as fast as it can without checking the keyboard 
input. You might want to Bugzilla this, because it happens a lot.


--
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

Re: How do I abort a handler in OS X???

[Mark Smith]

Sadly, cmd-period doesn't seem to do it. I'm on OS X.

I've adopted the habit of putting "if the optionKey is dwon then exit  
to top" at the start of the loop until I've debugged it enough to be  
sure it isn't going to be infinite...which is no help at all in your  
current predicament. You could try cmd-S before you force quit. I  
seem to remember that it actually worked one time, but I could be wrong.


Best,

Mark


On 26 Jun 2006, at 20:22, Jim Carwardine wrote:

Hi Folks... I've just upgraded to Rev 2.7.2 in OS X and can't seem  
to get
command/period to abort a handler in an infinite repeat loop.  It  
that only
a Classic function?  How do I do it in OS X?  I can't look it up in  
the rev
docs because my IDE is busy inside my repeat loop which I can't  
abort.  I'd
like to be able to save the script changes so I don't want to force  
quit.


How do I abort a handler?  Jim
--



___
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: How do I abort a handler in OS X???

[Mark Talluto]

Oh.  Sorry.  On a Mac you hit the command & period button.  I am not  
sure what the key presses are for Windows.  I am sure someone here  
knows.


-Mark Talluto

On Jun 26, 2006, at 12:32 PM, Jim Carwardine wrote:


No, I need to physically abort it.  I can't change the code when it is
executing... Jim

on 6/26/06 4:24 PM, Mark Talluto wrote:



On Jun 26, 2006, at 12:22 PM, Jim Carwardine wrote:


Hi Folks... I've just upgraded to Rev 2.7.2 in OS X and can't seem
to get
command/period to abort a handler in an infinite repeat loop.  It
that only
a Classic function?  How do I do it in OS X?  I can't look it up in
the rev
docs because my IDE is busy inside my repeat loop which I can't
abort.  I'd
like to be able to save the script changes so I don't want to force
quit.

How do I abort a handler?


exit handerName

In some cases, you might want to:  exit to top


Mark Talluto


--

www.TalentSeeker.ca   www.HiringSmart.ca/ns   www.KeepingTheBest.ca/ns


Own Your Future Consulting Services Limited,
23 Shoal Cove Road, Seabright, Nova Scotia, Canada.  B3Z 3A9
Phone: 902-823-2339. Fax: 902-823-2139




___
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: How do I abort a handler in OS X???

[Jim Carwardine]

No, I need to physically abort it.  I can't change the code when it is
executing... Jim

on 6/26/06 4:24 PM, Mark Talluto wrote:

> 
> On Jun 26, 2006, at 12:22 PM, Jim Carwardine wrote:
> 
>> Hi Folks... I've just upgraded to Rev 2.7.2 in OS X and can't seem
>> to get
>> command/period to abort a handler in an infinite repeat loop.  It
>> that only
>> a Classic function?  How do I do it in OS X?  I can't look it up in
>> the rev
>> docs because my IDE is busy inside my repeat loop which I can't
>> abort.  I'd
>> like to be able to save the script changes so I don't want to force
>> quit.
>> 
>> How do I abort a handler?
> 
> exit handerName
> 
> In some cases, you might want to:  exit to top
> 
> 
> Mark Talluto

-- 

www.TalentSeeker.ca   www.HiringSmart.ca/ns   www.KeepingTheBest.ca/ns


Own Your Future Consulting Services Limited,
23 Shoal Cove Road, Seabright, Nova Scotia, Canada.  B3Z 3A9
Phone: 902-823-2339. Fax: 902-823-2139




___
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: How do I abort a handler in OS X???

[Mark Talluto]

On Jun 26, 2006, at 12:22 PM, Jim Carwardine wrote:

Hi Folks... I've just upgraded to Rev 2.7.2 in OS X and can't seem  
to get
command/period to abort a handler in an infinite repeat loop.  It  
that only
a Classic function?  How do I do it in OS X?  I can't look it up in  
the rev
docs because my IDE is busy inside my repeat loop which I can't  
abort.  I'd
like to be able to save the script changes so I don't want to force  
quit.


How do I abort a handler?


exit handerName

In some cases, you might want to:  exit to top


Mark Talluto
--
CANELA Software
http://www.canelasoftware.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

How do I abort a handler in OS X???

[Jim Carwardine]

Hi Folks... I've just upgraded to Rev 2.7.2 in OS X and can't seem to get
command/period to abort a handler in an infinite repeat loop.  It that only
a Classic function?  How do I do it in OS X?  I can't look it up in the rev
docs because my IDE is busy inside my repeat loop which I can't abort.  I'd
like to be able to save the script changes so I don't want to force quit.

How do I abort a handler?  Jim
-- 



___
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