Alternate ways to perform this command are:
When you choose Run|Run Project, JBuilder automatically compiles the file or project before running it, if the Compile Before Running option is set on the Run page of the Project Properties dialog box.
Use the Project Properties dialog box (Project|Project Properties) to change compiler options. When working with partial projects, make sure that the Make Stable Packages option is unchecked.
See also:
Building Applications with JBuilder: Compiling Java programs
When you choose Run|Debug Project, JBuilder automatically compiles the file or project before debugging it, if the Compile Before Debugging option is set on the Run page of the Project Properties dialog box.
To place symbolic debugging information into the class files, use the Include Debug Info option on the Compiler page of the Project Properties dialog box. (This is the default.)
When you start the debugger, the debugger user interface displays in the message pane below the AppBrowser. For more information, see the topic called "Debugger user interface."
Alternate ways to perform the Debug command are:
See also:
Building Applications with JBuilder: Debugging Java programs
Building Applications with JBuilder: Overview of the debugging process
See also:
Building Applications with JBuilder: Setting runtime configurations
By default, when you initiate a debugging session with Run|Step Over, JBuilder moves the execution point to the first line of code that contains debugging information (this is normally a location that contains user-written code).
In addition to stepping over methods, you can trace into them as well. Use Run|Step Into to step into each line of a method call.
Alternate ways to perform the Step Over command are:
See also:
Building Applications with JBuilder: Stepping over a method call
The Step Into command executes the statement highlighted by the execution point and advances the execution point to the next executable statement.
In addition to tracing into methods, you can step over them, executing each method as a single element. See Run|Step Over for more information.
Alternate ways to issue the Step Into command are:
See also:
Building Applications with JBuilder: Stepping into a method call
Classes in the Classes with tracing disabled view will not be stopped in. It is possible to be in this situation, for example, when you step out of routine that was called from a class you didn't want to step into.
An alternate way to issue this command is to click the Step Out icon on the debugger toolbar.
You can use Run To Cursor to run your application and pause before the location of a suspected problem. You can then use Run|Step Over or Run|Step Into to control the execution of individual lines of code.
See also:
Building Applications with JBuilder: Running to the cursor location
See also:
Run|Run To Cursor
Building Applications with JBuilder: Running to the end of a method
The debugger pauses and positions the execution point on the next line of code to run. You can examine the state of your application at this point, then continue debugging by running, stepping, or tracing.
In addition to temporarily pausing an application or applet running in the debugger, you can also stop it and release it from memory by choosing Run|Program Reset, or pressing Ctrl+F2.
See also:
Building Applications with JBuilder: Running and suspending your program
Alternate ways to issue the Resume command are to:
See also:
Building Applications with JBuilder: Debugging sessions
Use Reset to restart an application from the beginning, such as when you make a change to the code and want to run again from the beginning, or if variables or data structures become corrupted with unwanted values.
When you reset an application, JBuilder performs the following actions:
An alternate way to issue the Reset command is to click the Reset icon on the debugger toolbar.
See also:
Building Applications with JBuilder: Resetting the program
The Evaluate/Modify dialog box lets you view and modify the values of object properties while the program is suspended. However, to view a property, you need to explicitly specify the property name. For example, you can enter the following expression to evaluate the Caption property of Button1:
Button1.Caption
Alternate ways to perform an Evaluate|Modify command are:
See also:
Building Applications with JBuilder: Evaluating expressions
The Data watches view displays the watches and lets you add, edit, delete, enable, and disable watches from its context menu.
Alternate ways to perform the Add Watch command are to:
See also:
Building Applications with JBuilder: Watching expressions
A breakpoint is a place in your program where execution temporarily stops. When the debugger reaches a breakpoint, it pauses your program. You can specify any number of breakpoints in your code.
When you set a breakpoint, the line on which the breakpoint is set becomes highlighted, and a stop-sign glyph appears in the left margin of the breakpoint line.
Each breakpoint listing shows the following in the Data and code breakpoints view:
See also:
Building Applications with JBuilder: Using breakpoints
UBuilding Applications with JBuilder: Setting breakpoints
See also:
Building Applications with JBuilder: Setting breakpoints
This is a feature of JBuilder Professional and Enterprise.
Displays the Classes With Tracing Disabled dialog box, the list of classes for which tracing has been disabled.
See also:
Building Applications with JBuilder: Controlling which classes to trace into