Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!ukma!nrl-cmf!ames!ucbcad!ucbvax!ernie.Berkeley.EDU!carlson
From: carlson@ernie.Berkeley.EDU (Richard L. Carlson)
Newsgroups: comp.sys.amiga
Subject: Re: Suggestion for 1.3 (or ...)
Message-ID: <21943@ucbvax.BERKELEY.EDU>
Date: Wed, 25-Nov-87 01:50:09 EST
Article-I.D.: ucbvax.21943
Posted: Wed Nov 25 01:50:09 1987
Date-Received: Sat, 28-Nov-87 10:45:58 EST
References: <1106@sugar.UUCP>
Sender: usenet@ucbvax.BERKELEY.EDU
Reply-To: carlson@ernie.Berkeley.EDU.UUCP (Richard L. Carlson)
Organization: University of California, Berkeley
Lines: 21
Keywords: system requesters


Here's yet another suggestion for eliminating a minor inconvenience:

Currently, when a system requester is created, the workbench screen is
implicitly brought to the front so that the requester is guaranteed to
appear.  However, when the requester is satisfied, workbench is *left*
as the frontmost screen; and Amiga-M must be used to return to the
previously-frontmost screen.

I would certainly not classify this as a major problem, but I think that
restoring the frontmost screen when a requester disappears would improve
the user interface of the Amiga (and I can imagine an inexperienced
user calling up, say, an interlaced VT100, getting a system request to
re-insert the workbench disk [to load in the serial.device], re-inserting
workbench, and then wondering where his VT100 screen went).  Is there a
major problem with restoring a screen that I have overlooked?  Or is this
just something that doesn't bother people (except me :-)?

-- Richard Carlson
   carlson@ernie.Berkeley.EDU
   ...!ucbarpa!ernie!carlson