Browse Prior Art Database

Common Screen Driver for Utilities

IP.com Disclosure Number: IPCOM000062687D
Original Publication Date: 1986-Dec-01
Included in the Prior Art Database: 2005-Mar-09
Document File: 3 page(s) / 77K

Publishing Venue

IBM

Related People

Lin, C: AUTHOR [+3]

Abstract

A common screen driver is described which presents a series of prompts and messages to the user. This eliminates the need to develop separate screen drivers in each utility and thus reduces development time and code space. This screen interface incorporates many unique features, such as a ringed cursor motion among the prompts, optional use of input handlers for each of the prompts, initial message display, interspersed messages and prompts, regeneration of the screen, and optional message display when regenerating the screen. An example of a screen generated and controlled by the screen driver is shown in Fig. 1. When the screen driver receives control, the top line is displayed using the address contained in the control table shown in Fig. 2.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 55% of the total text.

Page 1 of 3

Common Screen Driver for Utilities

A common screen driver is described which presents a series of prompts and messages to the user. This eliminates the need to develop separate screen drivers in each utility and thus reduces development time and code space. This screen interface incorporates many unique features, such as a ringed cursor motion among the prompts, optional use of input handlers for each of the prompts, initial message display, interspersed messages and prompts, regeneration of the screen, and optional message display when regenerating the screen. An example of a screen generated and controlled by the screen driver is shown in Fig. 1. When the screen driver receives control, the top line is displayed using the address contained in the control table shown in Fig. 2.

(Image Omitted)

Next, each of the messages and prompts is displayed on the proper line. The default answers to block prompts are enclosed in brackets, and the default answers to text prompts displayed. The Fkey labels are displayed across the bottom of the screen. The address of the initial message is checked for a zero; if it is nonzero, the initial message is displayed. The prompt handler is called using the information contained in the prompt/message table to process the first prompt. Messages and prompts may occur interspersed and in any order; messages are recognized by a zero entry in the default answer address field of the prompt/message table entry. When control returns from the prompt handler, the key that caused control to return is checked. a. If F8 was pressed, then the directory list handler is called. b. If Escape was pressed, then control returns immediately to the caller of the screen driver. c. Else, the input handler field of the prompt/message table entry is checked for a zero; if it is nonzero, control is

passed to an

input handler that may do such things as validate

answers. When control returns from an input handler, the input handler return code is checked for an error. a. If an error has occurred and the key that caused control to re turn from the prompt handler was the execute or exit Fkey, then the execute or exit condition is reset so that the prompt handl...