Difference between revisions of "83Plus:BCALLs:401E"
From WikiTI
m (→Inputs: Linked flags) |
m (it's -> its, link to AppInit, minor formatting change) |
||
| Line 7: | Line 7: | ||
Starts the system monitor. The system monitor will take over the system, and | Starts the system monitor. The system monitor will take over the system, and | ||
report events to the application via the monitor vectors. The application must | report events to the application via the monitor vectors. The application must | ||
| − | set | + | set its own monitor vectors with [[83Plus:BCALLs:404B|AppInit]] before calling Mon. Control of the |
application will never be returned from Mon. | application will never be returned from Mon. | ||
=== Inputs === | === Inputs === | ||
| − | * [[83Plus:Flags:28|AppAllowContext, (IY + APIFlg)]] = 1 to allow Mon to pass context keys, like | + | * [[83Plus:Flags:28|AppAllowContext, (IY + APIFlg)]] = 1 to allow Mon to pass context keys, like kYequ to the cxMain routine. |
| − | + | ||
* [[83Plus:Flags:0C|CurLock, (IY + curFlags)]] = 1 to lock the cursor off | * [[83Plus:Flags:0C|CurLock, (IY + curFlags)]] = 1 to lock the cursor off | ||
Revision as of 12:59, 21 July 2007
Synopsis
Official Name: Mon
BCALL Address: 401E
Starts the system monitor. The system monitor will take over the system, and report events to the application via the monitor vectors. The application must set its own monitor vectors with AppInit before calling Mon. Control of the application will never be returned from Mon.
Inputs
- AppAllowContext, (IY + APIFlg) = 1 to allow Mon to pass context keys, like kYequ to the cxMain routine.
- CurLock, (IY + curFlags) = 1 to lock the cursor off
Outputs
- none
Registers Destroyed
- ??
Comments
The system NEVER returns from this B_CALL. The programmer should find alternative methods of regaining control and exiting such as hooks, cxMain, etc.
