MessageTrans_ErrorLookup (changes)
Showing changes from revision #1 to #2:
Added | Removed | Changed
MessageTrans
» SWI Calls
» MessageTrans_ErrorLookup
MessageTrans_ErrorLookup
(SWI &41506)
| Entry | |
|---|---|
| R0 | Pointer to error block |
| R1 | Pointer to 4-word data structure, or 0 for global messages |
| R2 | Pointer to buffer for result, or 0 to use internal buffer |
| R3 | Size of buffer |
| R4 | Pointer to parameter 0, or 0 if none |
| R5 | Pointer to parameter 1, or 0 if none |
| R6 | Pointer to parameter 2, or 0 if none |
| R7 | Pointer to parameter 3, or 0 if none |
| Exit | |
|---|---|
| R0 | Pointer to error buffer used |
| V flag set |
Use
This SWI is used to translate a message token within an error block, with optional parameter substitution.
Notes
This SWI is like MessageTrans_Lookup except that it is passed a token in an error block in R0. The data structure is in R1, not R0. If the token is not found in the message file specified, it will be searched for in the global message file.
If R2 = 0 on entry MessageTrans will use an internal buffer. There are 2 for calls from IRQ routines, and 10 for foreground processes, which it cycles through.
To check that your error message was looked up (rather than MessageTrans itself reporting an error) verify that the error number in the returned block is the same as that passed in.
See also
Social
and
ROOL Store
Buy RISC OS Open merchandise here, including SD cards for Raspberry Pi and more.