Next: Optimisations
Up: Execution with Grace
Previous: Fine Steps
Each user interface action, e.g. selecting a menu item, pressing a button
or typing a key creates an event which must be processed by Grace .
When Grace stops after a normal labelling step
and highlights the next selected variable,
it accepts and processes all events.
This is a synchronous stop.
Grace can also be stopped by some special conditions outside
of normal step boundaries, and then it accepts
only a subset of all possible events.
In particular, manual selection and labelling is not accepted.
These are asynchronous stops.
Synchronous stop conditions are:
- After the next normal step, when pressing the STEP
button.
- When a variable breakpoint has been hit.
- When the program reaches a requested condition,
a given step number or depth.
- When the user types Ctrl-C.
Asynchronous stops are:
- After the next fine step, when pressing Shift+STEP,
unless it ends on a normal step boundary.
- When a solution is found.
- When grace_stop/1
is called.
- At the end of the whole program (depends also on the option
restart
).
- At the beginning of minimisation with grace_minimize/1,2.
Next: Optimisations
Up: Execution with Grace
Previous: Fine Steps
Micha Meier
Tue Jul 2 10:07:34 MET DST 1996