| Allegro CL version 8.2 Object described on page has changed in 8.2. 8.1 version |
The Run Menu displays commands for testing forms and projects and for using tools that affect or report on how a program runs. The commands on the menu are:
When you run a project (as opposed to running a single form with Run Form), the windows of the project are created in their own window hierarchy (or hierarchies), completely separate from IDE window hierarchy. This is done so that running the project from the IDE will emulate the eventual standalone application as closely as possible for more complete debugging.
But this also means that IDE keyboard shortcuts are not available while the running project windows are selected, and the entire running project may get buried behind the IDE, since the whole IDE is always either in front of or in back of the entire running project. You can switch between the running project and the IDE as you would between two applications, by using the Windows Task Bar or the Alt-Tab gesture.
The behavior is different when running a single form (with the Run Form command). In that case, the running window will be owned by the invisible IDE owner window, and therefore it can be intermingled among the various IDE windows and you can still use IDE keyboard shortcuts and so on. If you run a project when it is already running, the current running instance is first halted (and its windows are closed) and then the project is run again from scratch.
When you run a form, the running window for the form is owned by the invisible IDE owner window. Therefore, the running window behaves as if it were part of the IDE. That is, the window may be intermingled among the various IDE windows, and the IDE keyboard shortcuts may still be used. This is done so that the IDE is still conveniently available while quickly testing single forms.
This behavior is different from the behavior when running the whole project by choosing the Run Project menu command or clicking the Run button on the Toolbar. When a project is run, the project's windows are created in their own hierarchy completely separate from the IDE, so that the running project will emulate the eventual standalone application as nearly as possible for more complete debugging.
If you run a form which is already running, the current running window is first closed, and then it is created and run again from scratch.
If the selected object is the name of a generic function, then a pop-up menu will appear asking which method to breakpoint; the special All choice will breakpoint all methods of the generic function.
If the Stepper Dialog is currently selected, and the Definition Pane has the keyboard focus and is highlighting a selected form, then the breakpoint will be set on the selected form inside the function being stepped through. The selected form is the one under the mouse if any, and otherwise the form at which the stepper is stopped.
(In releases prior to 8.2, the breakpoint commands on the Run menu worked with the trace facility's breakpoint option, rather than emulating the top-level :break command. To emulate the old behavior, you would need to use the trace macro itself.)
Copyright (c) 1998-2016, Franz Inc. Oakland, CA., USA. All rights reserved.
The object described on this page has been modified in the 8.2 release; see the Release Notes.
Created 2016.6.21.
| Allegro CL version 8.2 Object described on page has changed in 8.2. 8.1 version |