How can I get my large, complex application to visualize?
How can I open a source file and set a break point without first running to that point?
How can I reset the RetroVue preferences to their defaults?
Why won't my source code display in RetroVue? I've set the sourcepath correctly, and I know the source files are in the right place.

• Using a customized script to launch;
• Dynamically loading classes from .jars not on the classpath;
• One of the .jars on the classpath is
  • not augmenting
  • throwing exceptions when augmented; etc.

You can augment only particular .jar files "by hand" with some variation of the following:

java -cp $PATH_TO_RV/retro.jar com.visicomp.Augment Foo.jar

The augmented jar will be saved in a directory called

tmp/AugDir/Foo.jar

You can then replace the normal .jar with the augmented .jar (taking care to save your normal .jar). Then, add retro.jar to the classpath, and a .jnl (journal) file will be produced. Then you can visualize the journal file with

java -jar retro.jar Foo.jnl

Top

How can I open a source file and set a break point without first running to that point?
Make the class browser visible by opening the "drawer" splitpane divider (on the left edge of the screen). Browse to the class you are interested in, and then the method of interest. Right-click on this method to bring up the popup menu, and select "Go To->Source". Assuming you've set the sourcepath correctly (see launcher documentation for details), the appropriate source file will appear on screen and automaticaly scroll to the method of interest. Top

How can I reset the RetroVue preferences to their defaults?
Delete a file called .retrovue in your home directory. The next time you start RetroVue, the preferences should be reset to the defaults. Top

Why won't my source code display in RetroVue? I've set the sourcepath correctly, and I know the source files are in the right place.
Your .class or .jar files may not have the debugging information that allows us to load the correct source file. Current versions of javac, when invoked directly, insert this information. However, the popular Java build tool Ant by default invokes javac and produces .class files without any location information. If you have this problem, and are using ant, try modifying your build.xml file similar to this (for each javac task):

<javac srcdir="${build}/${src}"
destdir="${build}/product"
debug="on" />

Please note: the last line will insert the location information. See the ant documentation for more information. Top