Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Sharing OS/2 Presentation Manager Controls Across Multiple Dialog Boxes

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

Publishing Venue

IBM

Related People

Van Gennip, EG: AUTHOR [+2]

Abstract

In the CODE/400 and CODE/370 products there is a need to share some information across three dialogs (OPEN, SAVEAS, GET dialogs). This information is stored in four OS/2* Presentation Manager* (PM) controls and four titles corresponding to these controls. These controls are an Entry Field, a Drop-down combo box and two Listboxes. Whatever the user enters into these fields on the OPEN dialog, for example, must also appear on the SAVEAS and GET dialogs in the exact same format. Similarly for the GET and SAVEAS dialogs the information must appear on the OPEN dialog. As the amount of information which could be in these fields can be very large it was determined that performance would be too poor to copy the same information three times, into the three dialogs.

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

Sharing OS/2 Presentation Manager Controls Across Multiple Dialog
Boxes

      In the CODE/400 and CODE/370 products there is a need to share
some information across three dialogs (OPEN, SAVEAS, GET dialogs).
This information is stored in four OS/2* Presentation Manager* (PM)
controls and four titles corresponding to these controls.  These
controls are an Entry Field, a Drop-down combo box and two Listboxes.
Whatever the user enters into these fields on the OPEN dialog, for
example, must also appear on the SAVEAS and GET dialogs in the exact
same format.  Similarly for the GET and SAVEAS dialogs the
information must appear on the OPEN dialog.  As the amount of
information which could be in these fields can be very large it was
determined that performance would be too poor to copy the same
information three times, into the three dialogs.  Thus, the idea of
using the same controls and sharing them across the three dialogs.

      This is done by creating a fourth dialog, named the selection
dialog.  This dialog 'owns' the entry field, dropdown combo box, two
listboxes and their four titles.  This allows one subclass procedure
to handle all requests for these shared controls.  The subclass
procedure knows which of the OPEN, SAVEAS or GET dialogs is currently
active, thus it can process common requests and pass along the dialog
specific requests to the proper dialog.  In this way the shared
controls
are maintained exactly the same for the OPEN, SAVEAS and GET dialogs.

      One of the funtions of the CODE/400 product and CODE/370
product is to allow a customer to access files from a host (OS/2, VM,
MVS or OS/400*) and work with the files on the workstation.  The
product provides list of files on the host and the customer selects
which to work on.  This disclosure relates to how those lists of host
files are presented and maintained.  NOTE: OS/2 is not a true 'host'
but for the purposes of the CODE product and access files we treat it
as another host type.

      The 'information to be shared' as described above is the host
file information the CODE products extract from the various hosts.

      To implement the above idea we created a fourth dialog, named
the Selection dialog.  This is really a dummy dialog, which is
created when the CODE product initializes.  The selection dialog
'owns' the four controls which are shared by the OPEN, SAVEAS and GET
dialogs as well as the four titles.  Also during initialization of
the four titles, the entry field, dropdown combo box, two listbox
controls and the owner and parent set to the selection dialog are
dynamically created.  The position and size can be adjusted
dynamically.  Initially these four controls are empty.

      When the user selects one of the OPEN, SAVEAS, or GET dialogs
then the entry field, dropdown combo box, two listboxes and four
title controls are updated so that the owner and parent is now the
dialog about to be displayed (OPEN for example). ...