[OT] Re: [ANN] tRev's new 'decoder' now showing...video is up!

[Jerry Daniels]

Brian,

Have you ever noticed the dots in Rev's debugger? How, if your script  
has very many lines at all, the dots can't keep pace with scrolling,  
returns, etc.? I have. Not pretty, to say the least. So, no images  
floating around for me, thank you.

Also, keeping a separate array of breakpoints and keeping them in sync  
with the actual code is not easy in a world where tRev is not the only  
script editor. I used to have lots of these sorts of "proprietary"  
approaches. It always came back to bite me in the behind when people  
traded code with others or used more than one editor.

So, a couple years ago, i decided to use text to indicate a  
breakpoint. Easy to see, easy to delete, follows the code wherever it  
goes, never gets out of sync. It's all good. Now that we've added  
record id's as comments following the word "breakpoint", we can attach  
loads of data to a breakpoint.

I'm warming up to the idea, too! I think everyone needs to buy the  
product now!!

Best,

Jerry Daniels
Watch tRev - The Movie
http://reveditor.com/trev-the-movie

On Aug 25, 2009, at 7:13 PM, Brian Yennie wrote:

> Off the cusp idea -- what about just making "breakpoints" completely  
> visual in tRev? Perhaps use an image with an arrow and some sort of  
> useful icon? That way you'd maintain the use of actual breakpoints  
> for all of the reasons you outlined, but just give the user  
> something tRev-specific to look at.
>
>> Hey, Dick! Good to hear from you.
>>
>> I would need to deal with the whole name space thing...if some  
>> other program used checkpoint, etc.
>>
>> Using "breakpoint" has two sizeable advantages over alternatives  
>> (now that I'm really considering your suggestion):
>>
>> 1. I don't have to worry about another program using it.
>>
>> 2. It has a use when tRev is not in use. E.g., when you give  
>> someone else your code and they don't have tRev (because of a  
>> religious injunction or something).
>>
>> Great idea, though. I'll play around with it some. Thanks.
>>
>> Best,
>>
>> Jerry Daniels
>> Watch tRev - The Movie
>> http://reveditor.com/trev-the-movie
>>
>> On Aug 25, 2009, at 6:40 PM, Dick Kriesel wrote:
>>
>>> On 8/25/09 3:18 PM, "Jerry Daniels" <jerry.daniels at me.com> wrote:
>>>
>>>> I agree TOTALLY with the request, but alas, Rev forbids it.
>>>
>>> Hi, Jerry.  Could you proceed without Rev's traceback message?
>>>
>>> on mouseUp
>>> put 1 into t1
>>> put 2 into t2
>>> checkPoint
>>> end mouseUp
>>>
>>> command checkPoint
>>> set the debugcontext to line -2 of the executioncontexts
>>> global gREVVariableWatcherValue
>>> debugdo "revDebuggerGrabValue the variableNames"
>>> repeat for each item tVariableName in line 2 of  
>>> gREVVariableWatcherValue
>>>   debugdo "revDebuggerGrabValue" && tVariableName
>>>   put gREVVariableWatcherValue into tVariables[tVariableName]
>>> end repeat
>>> set the debugcontext to empty
>>> -- ... "store the full context into a database"
>>>
>>> breakpoint -- just so you can see tVariables[]
>>> end checkPoint
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your  
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-revolution