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

Pending Apply/ Close Program

IP.com Disclosure Number: IPCOM000122002D
Original Publication Date: 1991-Oct-01
Included in the Prior Art Database: 2005-Apr-04
Document File: 1 page(s) / 57K

Publishing Venue

IBM

Related People

Weber, O: AUTHOR

Abstract

This article describes a mechanism for insuring that child windows under OS/2* Presentation Manager* (PM) are properly closed as expected by the user, since child windows do not always close as expected, even when the parent window is closed. An API is need which will intervene in the required situations to insure that all child windows close properly, even when the situations are complicated by timing problems.

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

Pending Apply/ Close Program

      This article describes a mechanism for insuring that
child windows under OS/2* Presentation Manager* (PM) are properly
closed as expected by the user, since child windows do not always
close as expected, even when the parent window is closed.  An API is
need which will intervene in the required situations to insure that
all child windows close properly, even when the situations are
complicated by timing problems.

      The problem exists when window_proc_1 for window_1, creates a
child window, window_2, whose window procedure is window_proc_2.
Window_1 presents, among other pushbuttons, an APPLY button.  The
purpose of the APPLY button is to save the user's changes, but leave
the window displayed for additional viewing or updating, as opposed
to destroying the window as is desirable with the SAVE or CANCEL
operation. The following scenario demonstrates the problem:  The user
selects APPLY on window_2.  An hourglass appears whenever the mouse
pointer is over window_2, until the apply operation completes. While
the APPLY operation is still underway, the user moves the mouse
pointer over window_1. The hourglass changes back to an arrow, and
the user double-clicks on the system menu of window_1, requesting to
close the application.  Window_proc_1 sends a WM_CLOSE message to
window_proc_2.  This causes a dilemma.  If window_proc_2 honors the
WM_CLOSE request, the application is closed before the APPLY
completes, and the user's c...