use-revolution Digest, Vol 33, Issue 42

[Jeffrey Reynolds]

i have always done this plus a flag for a development variable and  
dont bother stripping them later, they only work if the variable is  
set right (by me when in development mode).

global isitdev
if the optionkey is down and isitdev is "yessirrebob" then exit  
[handler]

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.

cheers,

jeff

Jeffrey Reynolds




On Jun 26, 2006, at 5:18 PM, use-revolution-request at lists.runrev.com  
wrote:

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