Browse Prior Art Database

Single Presentation Space for Messages From Multiple Operations

IP.com Disclosure Number: IPCOM000119681D
Original Publication Date: 1991-Feb-01
Included in the Prior Art Database: 2005-Apr-02
Document File: 2 page(s) / 85K

Publishing Venue

IBM

Related People

Banning, KR: AUTHOR [+6]

Abstract

Multi-tasking operating systems allow a single user to perform multiple operations simultaneously. When presented in a normal windowed user interface environment, this capability can produce uncertainty in the user when system generated messages occur. Traditionally, non-zero return codes from the application software or system software resulted in message or other dialogs being presented to the user. In a windowed environment this may result in multiple message windows for the same task being performed on different objects. One alternative is to present multiple messages. This is wasteful of the system resources and confusing to the user as they must read each message in turn to find the events of interest. The disclosed single message space provides a better solution.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 53% of the total text.

Single Presentation Space for Messages From Multiple Operations

      Multi-tasking operating systems allow a single user to
perform multiple operations simultaneously.  When presented in a
normal windowed user interface environment, this capability can
produce uncertainty in the user when system generated messages occur.
Traditionally, non-zero return codes from the application software or
system software resulted in message or other dialogs being presented
to the user.  In a windowed environment this may result in multiple
message windows for the same task being performed on different
objects.  One alternative is to present multiple messages.  This is
wasteful of the system resources and confusing to the user as they
must read each message in turn to find the events of interest.  The
disclosed single message space provides a better solution.

      When the user is engaged in a dialog with a computer program to
perform a common action on multiple objects, the user selects the
objects and commits the operation.  Each object is being manipulated
in a separate thread to minimize the response time.  In this way,
each is a separate process and capable of completing or failing
independently of the other requests.  The dialog that began all the
requests must continue with support to the user on the status of the
requests.  If traditional message boxes are used, the user may become
overwhelmed with a series of messages that cannot give a true state
of the request...