RISC OS Open
A fast and easily customised operating system for ARM devices
ROOL
Home | News | Software | Bugs | Bounties | Forum | Documents | Photos | Contact us
Account

OS_ReadEscapeState

Programmer's Reference Manuals
» Part 15 – SWI Calls
» OS
» OS_ReadEscapeState

OS_ReadEscapeState

(SWI &2C)
Entry
- -
Exit
C flag is set if an escape condition has occurred

Use

The purpose of this call is to check whether an escape condition has occurred

Notes

Once an escape condition has been detected, (either through this or for example, with OS_ReadC), it should be acknowledged with OS_Byte 126 or cleared using OS_Byte 124.

This call is useful if a program is executing in a loop which the user may want to escape from, but isn’t performing any input operations which would let it know about the escape.

Note that this may be called from an interrupt routine. However, OS_Byte 126 may not be, so if an escape is detected under interrupts, the interrupt routine must set a flag which is checked by the foreground task rather than try to acknowledge the escape itself.

See also

  • OS_Byte 124
  • OS_Byte 126
  • OS_ReadC
Created on December 1, 2009 14:41:52 by Alan Robertson (52)? (127.0.0.1)
Edit | Views: Print | Source | Linked from: Kernel notes, OS SWI Calls

Search the Wiki

Commercial use

For commercial enquiries, please contact the owners of RISC OS, Castle Technology Ltd.

ROOL Store

The official C/C++ Development kit and more here.

Donate! Why?

Help ROOL make things happen – please consider donating!

Navigation

  • Home Page
  • All Pages
  • Recently Revised
  • Authors
  • Feeds
Site design © RISC OS Open Limited 2011 except where indicated
The RISC OS Open Instiki theme is based on Insitki's default layout

Valid XHTML 1.0  |  Valid CSS

Instiki 0.19.1(MML+)
This site runs on Rails

Hosted by Arachsys