De-construct your code with tRev's decoder!
Since this video was made, tRev's Breakpoint Manager has been spiffed-up and enhanced.
If you are not seeing breakpoints populate with data, remember the following:
- You have to have Rev in debug mode.
- Breakpoints don't get data until you run the code in Rev.
- Use the Decoder to set and clear breakpoints, don't try it by hand. Plain breakpoints created by hand are ignored by tRev.
You will have to quit tRev and restart it after updating to the Decoder. You do not, however, need to re-install with option key + launch. A simple restart is required because the Decoder uses a new data broker, and it won't be in use until you restart tRev.
Some Tips
- If you have dirty tabs (uncompiled code), you will be encouraged via dialog to close or compile all code before decoding it. Otherwise, code can get over-written.
- When you set a breakpoint in decode mode, not only will your code be compiled with the new breakpoint, but its stack will also be saved. This will keep you from accumulating orphaned breakpoints in decoder's database. This saving will NOT create archived copies of the stack. You can do that with the Save, Archive & Compile menu item under the File menu (command+s).
- When using the Breakpoint Manager (command+shift+b), you can now double click a line in its list of breakpoints, and the code for that object will appear in a tab with the appropriate breakpoint line selected in the code.
Also: there is now a new preference that lets you turn off or on auto-complete (aka clairvoyance).
Try tRev now:
Created by Daniels & Mara
