Browse Prior Art Database

Implementing Enhanced Container Record Auto-Visibility Support

IP.com Disclosure Number: IPCOM000115578D
Original Publication Date: 1995-May-01
Included in the Prior Art Database: 2005-Mar-30
Document File: 4 page(s) / 150K

Publishing Venue

IBM

Related People

Johnson, DK: AUTHOR [+2]

Abstract

The OS/2* container control is one of the most used and most powerful controls available in the Presentation Manager* (PM) control set. It is a visual component whose specific purpose is to hold objects. These objects might represent such diverse entities as executable programs, database records, graphics images, or word processing files. The objects in a container may be visually represented by icons, bitmaps, text strings, or various combinations thereof.

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

Implementing Enhanced Container Record Auto-Visibility Support

      The OS/2* container control is one of the most used and most
powerful controls available in the Presentation Manager* (PM) control
set.  It is a visual component whose specific purpose is to hold
objects.  These objects might represent such diverse entities as
executable programs, database records, graphics images, or word
processing files.  The objects in a container may be visually
represented by icons, bitmaps, text strings, or various combinations
thereof.

      It is not unusual for a container control to hold several
hundred or more objects or container records.  With this number of
container records to manage, it is important to provide users with
methods to quickly access a desired record.  The OS/2 Workplace Shell
has implemented one such method in the form of a find function.  The
Workplace Shell find function displays a message box allowing the
user to enter a search string which is then used to search all of the
container records.  Any records matching the search string are
displayed in a new container.

      While this is a useful feature, many users in certain
circumstances would like to have added flexibility concerning the way
the container find function is implemented.  In many cases it would
be useful to have a find function that finds the desired record and
scrolls it into the visible region of the container being searched
rather than putting found records into a new separate container.
This would certainly be helpful any time position relationships among
records in a container are important.

      This disclosure describes an implementation of the find
function that will find a desired record within a container and will
insure that the found record will be displayed in the visible portion
of that container.  All necessary scrolling of the container will be
done automatically in order to bring the matching record into view.

      The find function might be triggered in several different ways.
One implementation could begin by presenting to the user a dialog
that contains an entry field where the user enters information used
to search for a matching container record.  This information could be
the text of the record or perhaps some other record attribute known
to the user and kept track of by the application.  The application
might also invoke the find function under the covers in response to
some user interaction which requires the display of a certain
container record.

      When the find function is invoked, container records are
searched to determine if there is a record that matches the
particular attribute being used for the search.  If a match is found,
the CM_SETRECORDEMPHASIS message with the CRA_CURSORED flag set is
sent to the container so that the matching record will obtain the
focus.  This provides visual feedback of the matching record to the
user.  It is then determined whether any vertical or hori...