Progress
AppBuilder
Developer’s Guide


Test-driving Your Design

At any time during an AppBuilder session, you can test the current design window workspace. When you run a design window, you are in fact running a temporary procedure file. If you read a procedure file into AppBuilder and make changes to the design window, the temporary file reflects those changes. However, until you save the procedure file, AppBuilder does not store the changes permanently. When you save your changes, AppBuilder overwrites the procedure file and preserves the changes. If you prefer to preserve the original state, do a Save As instead, or discard your changes by exiting without saving.

To run a design window, choose Compile Run, or choose the Run button, or press F2. Running the design window hides all windows except AppBuilder’s main window, and disables all of AppBuilder’s functionality except for a Stop button. AppBuilder displays the Stop button (eight-sided, red; it resembles the traditional US ’STOP’ road-traffic sign) in place of the Run button, as shown in Figure 2–21.

Figure 2–21: Stop Button

Choosing the Stop button stops the design window even if the window is, for example, caught in an endless loop. Choosing the Stop button always closes the run window and re-enables AppBuilder’s editing functionality.


Copyright © 2004 Progress Software Corporation
www.progress.com
Voice: (781) 280-4000
Fax: (781) 280-4095