Path: utzoo!attcan!uunet!ginosko!usc!bloom-beacon!LCS.MIT.EDU!MAP
From: MAP@LCS.MIT.EDU (Michael A. Patton)
Newsgroups: comp.windows.x
Subject: When (not) to lock out other input
Message-ID: <8908221752.AA29284@gaak.LCS.MIT.EDU>
Date: 22 Aug 89 17:52:15 GMT
References: <8908221345.AA02511@god.goldhill.com>
Sender: daemon@bloom-beacon.MIT.EDU
Organization: The Internet
Lines: 17


   Date: Tue, 22 Aug 89 09:45:09 EDT
   From: phil@goldhill.com


   There are cases where the user should not be allowed to do anything except
   respond to the popup. I have popup's that block all input in the case when
   a malloc has failed - the popup is to notify the user that such a condition
   has arisen and inform them that cleanup is about to occur and that a "safe"
   state in the application is to be returned to.

WRONG!  I would love to have some of my programs pop up a requestor
when this happens and let me go off to other windows killing things
off and then come back to the original popup and say something like
"Retry" since now the machine may have enough memory.  Most of them
just crash :-(.  There probably are some conditions where you HAVE to
respond, but I still haven't heard a good example.