Rev Editor

Just finished watching the video. That's a great feature but I've got a couple of questions and a feature request (of course):
1) If you have a breakpoint in say a repeat loop, does it remember every pass through the loop or only the last one?

2) It appeared in the video that the decoder just passed over some of the breakpoints, storing the info I'm sure, but not stopping. Does anything cause the decoder to stop (a la the debugger) or do you have to do something to trigger it to stop so you can look at your code?

3) Can the database be dumped to a file for later printing? Sometimes the bug takes looking at for a while which I prefer to do with paper rather than on the screen. I could live without it but it might be handy.

4) Is there a "trace in time" feature or display mode where you might be able to see not only what the decoder found at certain breakpoints but also when they happened in relation to each other (I'm thinking along the lines of a repeat loop that might have an if/else in it and it takes the "if" branch most of the time but sometimes takes the "else" branch. It might be nice to see when it takes each.

I know I'm suggesting a lot of complexity which is specifically what you are NOT trying to do with this and none of the above are game changers for me. Just nice little things to have.

As far as the feature request, it seems to me that one handy "Other" would be the defaultFolder. It would be nice to know where rev is looking for something. I'm not sure you can do that since you have to change to the tRev program to capture the state (I'm assuming) but it would be very nice to have.

That's enough until I actually start playing with it.

len morgan

1. Last loop gets recorded in this version.

I updated and then tested this new feature but kept getting a script editor on the breakpoint lines. So I quit and restarted tRev with the Option key down to force a re-install. Now the decoder works perfectly, so just a suggestion in case anyone else is having problems.
This was possibly because I didn't get the first update with the decoder but skipped to the second.

Anyway, it looks brilliant Jerry and certainly supplies what I need. I had need of a debugger just a few days ago and had to turn off tRev (gasp) and go back to the Rev editor :-( Now I will be OK.

Len, with wanting decoded info in loops, you could add conditional breakpoints e.g.

repeat with x = 1 to 10
if x = 1 then
breakpoint #123456789
else if x = 10 then
breakpoint #987654321
end if

-- do other stuff
end repeat

A bit more verbose, but I presume it would work.

Very nice, I may have to break down and purchase this.
Let me make a suggestion that you may consider for a future version. If possible every time you enter a loop count the iteration so that the user can see the count when inspecting a run. And for every if/else structure indicate the number of times you processed the if part and the number of times the else was executed. The total if and else iterations should equal the iteration count of the enclosing loop count.

Oh and say hello to U.S. Grant when you see him :)

Thanks for this update, It helps out so much. Keep up the great job Jerry.

is there some sort of log, on what is updated or changed when we click the blue update link. just wondering.

Not at this time, no log. But that's a good idea.

I have revised the initial tRev Decoder post with helpful hints. Worth a read.

I hope you can add a way to the decoder to do captures as you loop. Many times the stuff I am looking to debug is in a loop and it's not the last pass I am looking to capture.

Storing unique context data for every cycle of a loop would 1) make the loop run slowly and 2) destroy much of the simplicity of the decoder in terms of workflow and UI.

Cool. I thought this might be possible but I was not sure. That would do the trick and I agree with keeping it simple and fast.