Difference between revisions of "83Plus:BCALLs:4021"
From WikiTI
m (Links) |
|||
| Line 1: | Line 1: | ||
[[Category:83Plus:BCALLs:By Name:Monitor|MonForceKey]] [[Category:83Plus:BCALLs:By Name|MonForceKey]] [[Category:83Plus:BCALLs:By Address|4021 - MonForceKey]] | [[Category:83Plus:BCALLs:By Name:Monitor|MonForceKey]] [[Category:83Plus:BCALLs:By Name|MonForceKey]] [[Category:83Plus:BCALLs:By Address|4021 - MonForceKey]] | ||
| + | {{missinfo|Destroys}} | ||
== Synopsis == | == Synopsis == | ||
'''Official Name:''' MonForceKey | '''Official Name:''' MonForceKey | ||
| Line 17: | Line 18: | ||
=== Registers Destroyed === | === Registers Destroyed === | ||
| − | * | + | * unknown |
== Comments == | == Comments == | ||
Revision as of 20:06, 5 February 2008
This article is missing some information (namely Destroys). You can help WikiTI by filling in the missing information.
Synopsis
Official Name: MonForceKey
BCALL Address: 4021
Calls the system monitor but allows the programmer to push an initial key through cxMain. This is very much like Mon.
Inputs
- a = initial key press to simulate
- 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
- unknown
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.
Example
To simulate a key press by the user when first entering the system monitor:
;set up edit buffer ;... ld a,k8 B_CALL MonForceKey ;should see the number 8 appear in the edit buffer
