<nCause>
The parameter indicates the cause of a program termination. It is a numeric value for which #define constants exist in the XBP.CH file. These constants
are prefixed with XBP_QUITCAUSE_*.
Event XbpCrt():quit Foundation
Application will be terminated.
Syntax
:quit := {| nCause, nConfirm, self | ... } --> nConfirm
:quit ( <nCause>, <nConfirm> ) --> self
xbeP_Quit (1048633)
Parameters
<nConfirm>
The second parameter is used to confirm a program termination. The following #define constants can be used as valid values:
Constants for the second parameter
| Constant | Description |
|---|---|
| XBP_ALLOW *) | Program may be terminated |
| XBP_REJECT | Program must not be terminated |
|
|
Return
The code block must return a numeric value represented by a #define constant that is valid for <nConfirm>.
This method returns the object executing the method (self).
Description
The parameter <nConfirm> determines whether or not a program may be terminated. If a code block is assigned to the instance variable :quit, it must return a valid value for <nConfirm>. When the :quit() method is overloaded, the super class's method must be called with a valid value for the second parameter.
The xbeP_Quit event is generated when an Xbase++ application is terminated by its process being deleted from the task list. The task list is displayed by pressing the key combination Ctrl+Esc. It contains the titles of all windows where processes are active. Processes within the task list can be terminated by pressing the Delete key. If an Xbase++ application is terminated in this manner, the xbeP_Quit event is generated to which a reaction can be made.
On Windows platforms, the xbeP_Quit event is only generated upon system shutdown. That means, Windows does not generate an xbeP_Quit event when a program is terminated from the Task Manager. Instead, an xbeP_Close event is created. Only when a running process is about to be killed by the operating system's shutdown procedure does the program receive the xbeP_Quit event.
Feedback
If you see anything in the documentation that is not correct, does not match your experience with the particular feature or requires further clarification, please use this form to report a documentation issue.