OS_SpriteOp 60 (changes)

Showing changes from revision #3 to #4: Added | Removed | Changed

Programmer's OS Reference SWI Manuals Calls

» Part 15 – SWI Calls?OS_SpriteOp

» OS_SpriteOp 60 – Switch output to spriteOS

OS_SpriteOp 60 – Switch output to sprite

(SWI &2E)

Use

This call can be used to redirect screen output to a sprite image, or to return output back to the screen.

While output is redirected to a sprite, all VDU operations including text output, OS_Plot operations, and sprite rendering will act on the sprite and not the screen. The VDU Variables and Mode Variables will also reflect the change.

If the sprite has a palette, ColourTrans will use that palette for any colour translation or palette lookup operations. If the sprite has no palette, the current screen palette will be used instead. This may result in unpredictable behaviour if the current screen mode is a true colour mode.

If no save area is supplied in R3 or the save area is not yet initialised, the VDU state will be reset to the default for the sprite/screen mode. See VDU Save Area for more details on the state that save areas store.

Notes

To redirect screen output to a sprite mask, see OS_SpriteOp 61.

You must be careful to restore output back to the screen should an error occur. It’s recommended to install environment handlers so that unexpected errors (e.g. data aborts) can be fully accounted for.

To restore output back to its previous location, issue OS_SpriteOp with R0-R3 containing the values returned from this call.

The low-level PaletteV API only deals with the screen palette, and so does not adapt itself in any way when screen output is redirected to a sprite. Therefore any PaletteV calls made while output is redirected will manipulate the screen palette and not the sprite palette. Additionally, ColourTrans_WritePalette will return an error if called when output is redirected.

Service_SwitchingOutputToSprite will be issued by this call.

If a call is made to change the screen mode or switch video drivers while screen output is redirected, the output will be restored to the screen.

Redirecting output to a sprite without using a save area is strongly discouraged. The reason being that it can cause issues if you either directly or indirectly call a SWI which wants to use redirection internally (e.g. the font manager makes use of redirection to build the font cache). Save areas are small (currently under 512 bytes), so there is little reason to not use them.

See also

• Format Of Sprite
• Format Of Sprite Area
• OS_SpriteOp
• OS_SpriteOp 61
• VDU Save Area
• ColourTrans
• PaletteV