Point & click to modify your breakpoints in tRev!

Check out the new breakpoint editor:

(download)

Now you can point and click to modify your breakpoints FIVE different ways!

Check for Updates and get all this goodness. No need for a new tRev app download.

Try tRev now:

   

Created by Daniels & Mara

Feature Friday is Near-Future Friday

A book about tRev?

tRev is about to turn ONE!

Over the past year, our little buddy has grown far bigger than we ever expected. Features and functionality have been added at a spanking pace. And a number of these excellent additions have resulted from your user requests. Many thanks for the love.

However, there is one request which we've received from many of you that has thus far gone unrequited: a tRev Book.

So, now that the little guy is full grown, Mary Jane Mara (in-house technical writer and published author) and I (Jerry Daniels, tRev creator) are considering collaborating on a PDF book about the little dickens which would incorporate the QuickStart information already available for free on this site, plus:

  • All screenshots and explanatory articles posted over the past year updated as necessary, edited and re-organized into a single coherent document with hyperlinks to associated sections and items in the book
  • How-tos that help you capitalize on the interactivity of tRev's many feature sets, such as:
    • Using the Decoder to spend less time debugging
    • Using the Scratch Pad as a session-to-session work space
    • Handler management and centricity to improve project-to-project efficiency
    • Coding Standards that make auto-complete and debugging easier
  • Cherry-picked information from our RevMentor site
  • Complete list of tRev Shortcuts with hyperlinks to fuller explanations of associated features
  • Power user tips and tricks and Revolution gotchas

But let's face it. The Revolution market is small, and the tRev market even smaller. Therefore, to make this happen, we need 40 people who are willing to pre-buy the PDF for $25. To let us know if you are one of these knowledge-hungry users, SEND MJ AN EMAIL.

If and when we collect forty names, we'll send you each a link so you can make good on your pledge. If we can't collect enough pledges, the project will be dropped without anyone spending a dime – and, having made the offer, our consciences will be clear – and tRev will party on as always.

Conditional breakpoints and time traveler's wife

Learn all about making your tRev breakpoints super smart—and how to use our brand new Breakpoint Iterations navigator:

(download)

Conditional Breakpoints
 
Here are the new conditionals you can add to the breakpoints you make with tRev:
 
BREAKPOINT: #1274218486:once (only records the last time the breakpoint was called)
BREAKPOINT: #1274218486:clear (clears all data for the indicated breakpoint)
BREAKPOINT: #1274218486:stop (records data and then stops execution of code)
 
NOTE: Breakpoints with "clear" conditionals are placed before a repeat loop where a breakpoint with the same record number is being used. "clear" is not needed for any breakpoints that have "once" conditional.
 
BREAKPOINT: #1274218486:tVar=234
BREAKPOINT: #1274218486:tVar is 234
 
BREAKPOINT: #1274218486:tVar is not "fairfield"
BREAKPOINT: #1274218486:tVar<>12
 
BREAKPOINT: #1274218486:tVar>3
BREAKPOINT: #1274218486:tVar is greater than 3
 
BREAKPOINT: #1274218486:tVar<3
BREAKPOINT: #1274218486:tVar is less than 3
 
BREAKPOINT: #1274218486:tVar>=3
BREAKPOINT: #1274218486:tVar is greater than or equal to 3
 
BREAKPOINT: #1274218486:tVar<=3
BREAKPOINT: #1274218486:tVar is less than or equal to 3
 
BREAKPOINT: #1274218486:tVar contains 3
 
BREAKPOINT: #1274218486:tVar begins with 3
BREAKPOINT: #1274218486:tVar ends with 3
 
NOTE: To make your breakpoint conditionals more readable, you can use spaces in the portion of the conditional after the colon. Example...
 
BREAKPOINT: #1274218486: tVar = 234
 
More about Breakpoint Iterations (Time Traveler's Wife)
 
It didn't mention it in the video, but in addition to using cmd+shift+i, you can type either the return or escape keys to dismiss the Breakpoint Iterations pop-up.

If you have more iterations than your Breakpoint Iterations pop-up can house, you will see the last line of data truncated. Just move you mouse down to that last line in the pop-up and it will auto-scroll to let you see the line items that were hidden. Same goes for the top line when you've scroll down and there's now more line items on top.

Breakpoint Manager
 
The Breakpoint Manager now has the correct name for its button that clears out breakpoint data without removing the breakpoint itself from your code. All the tooltips reflect the new stuff you have seen today. Just turn on Headers and Extra Tool Tips from the prefs dialog.

Check for Updates and get all this goodness. No need for a new tRev app download.

Try tRev now:

   

Created by Daniels & Mara

Decoder lets you time travel through breakpoints!

Watch me travel in time with tRev's new decoder!

(download)

Setting and deleting breakpoints works the same. Breakpoint manager, too.

   

Think about it...

Now you can go back in time to see your code's context (content of vars, etc) a few minutes ago, or last week! This is great for repeat loops, but it also has other uses. Best of all, this context data is stored in your tRev database and none of this even touches Rev IDE.

Super Helpful Tip

If you want to reset the context data for a breakpoint to empty, just use the Breakpoint Manager to delete it. This only deletes the breakpoint's data, but leaves the breakpoint itself in your code!

NOTE: setting a breakpoint in a long repeat loop can slow down your code's execution.

Try tRev now:

   

Created by Daniels & Mara