Difference between revisions of "83Plus:BCALLs:51CD"
From WikiTI
(Created. See talk page.) |
Calc84maniac (Talk | contribs) (→Comments) |
||
(One intermediate revision by one other user not shown) | |||
Line 7: | Line 7: | ||
'''Minimum OS Version:''' 2.30 | '''Minimum OS Version:''' 2.30 | ||
− | Displays the number at [[83Plus:RAM:839F|839F]] | + | Displays the number at [[83Plus:RAM:839F|839F]] in large font. |
=== Inputs === | === Inputs === | ||
Line 22: | Line 22: | ||
== Comments == | == Comments == | ||
If you input something that would be less than the size of the output, it'll cut of the left hand side. Note: do not input A=0. If you input A larger than the size of the output, it will automatically cut off unneeded zeros at the front of the number. Do not use a excessively large value of A, though, or you may overflow some buffers. | If you input something that would be less than the size of the output, it'll cut of the left hand side. Note: do not input A=0. If you input A larger than the size of the output, it will automatically cut off unneeded zeros at the front of the number. Do not use a excessively large value of A, though, or you may overflow some buffers. | ||
+ | |||
+ | |||
+ | This can easily be used after [[83Plus:BCALLs:5014|B_CALL ArcChk]], but make sure you put in a valid value for a. | ||
+ | <br>--calc84maniac |
Latest revision as of 07:42, 9 February 2007
Synopsis
Unofficial Name: Disp32
BCALL Address: 51CD
Minimum OS Version: 2.30
Displays the number at 839F in large font.
Inputs
- A: maximum number of digits to display.
- 839F: 4 byte value. Most significant byte is first.
- curRow: Screen coordinates to display at.
Outputs
- Value displayed to screen.
Destroys
- AF, DE, HL
Comments
If you input something that would be less than the size of the output, it'll cut of the left hand side. Note: do not input A=0. If you input A larger than the size of the output, it will automatically cut off unneeded zeros at the front of the number. Do not use a excessively large value of A, though, or you may overflow some buffers.
This can easily be used after B_CALL ArcChk, but make sure you put in a valid value for a.
--calc84maniac