Wimp_CommandWindow

Introduction and Overview

From Select 1 onward Wimp_CommandWindow has been extended to provide information about its current state. This information can be used to determine whether or not an operation will trigger the display of a command window.

Under normal circumstances, when a task is started by the Window Manager the command window is marked as 'pending'. In this state, any output to the screen through the standard VDU calls will cause the command window to be opened; the state will then be set to 'open'. If the task registers with the Window Manager with Wimp_Initialise however, the command window is marked as 'inactive'. These states can be changed through the use of Wimp_CommandWindow as described in the PRMs.

The new call allows clients to identify what state the command window is currently in.

SWI Calls

Wimp_CommandWindow 2Wimp_CommandWindow_ReadStateSWI &400EF
Read the state of the command window
R0=2 (read state)
R0=State:
ValueMeaning
0The command window is inactive
1The command window is pending
2The command window is open
Interrupts are undefined
Fast interrupts are undefined
Processor is in undefined mode
Not defined

This SWI is used to find the state of the command window.