Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!cs.utexas.edu!yale!cmcl2!esquire!yost
From: yost@esquire.UUCP (David A. Yost)
Newsgroups: comp.lang.icon
Subject: Re: ProIcon Windows
Message-ID: <2064@esquire.UUCP>
Date: 8 Jun 90 13:38:08 GMT
References: <4356@uwm.edu>
Reply-To: yost@esquire.UUCP (David A. Yost)
Organization: DP&W, New York, NY
Lines: 16

In article <4356@uwm.edu> corre@csd4.csd.uwm.edu (Alan D Corre) writes:
>If the user closes
>the window by clicking on the box, and then the program attempts to close
>the window, there is a "hole" in the roster of windows, and the variable to
>which the integer is assigned has the same value, but no longer references a
>window. This causes an error.

The right way to handle this, I think, is for an icon procedure
to be called when the user clicks the close box.  Which is to say
that opening a window should do more than return an integer; it
should hook some procedures to be called when the user does
certain things to the window.

 --dave yost
   yost@dpw.com or uunet!esquire!yost
   Please ignore the From or Reply-To fields above, if different.