Path: utzoo!attcan!uunet!lll-winken!lll-tis!ames!mailrus!wasatch!sunset.utah.edu!u-jmolse
From: u-jmolse%sunset.utah.edu@wasatch.UUCP (John M. Olsen)
Newsgroups: comp.sys.amiga
Subject: WB 1.4 suggestions
Summary: Unloadwb would be nice.
Keywords: loadwb unloadwb multiple
Message-ID: <795@wasatch.UUCP>
Date: 14 Dec 88 06:00:27 GMT
References: <5031@garfield.MUN.EDU>
Sender: news@wasatch.UUCP
Reply-To: u-jmolse%sunset.utah.edu.UUCP@wasatch.UUCP (John M. Olsen)
Distribution: na
Organization: University of Utah, Computer Science Dept.
Lines: 35

Since everyone is suggesting things for 1.4, I thought I would add one
of the burrs under my saddle.  Have you ever wanted to UNloadwb?

Say you've used mwb (hi matt!) and have done a loadwb on each of your
screens.  Waddaya do when you want to close one of those screens down?
Or what do you do if you have an application that wants a little more 
CHIP RAM than you currently have, and you've already loaded workbench.

Also, one odd thing you can do is type "loadwb" more than once for the same
screen.  Try this for fun and excitement:

loadwb
<open up some drawers (call them A)>
loadwb
<open up the same drawers again (call them B)>
<try to drag a file from copy A to copy B>

At least it's smart enough to know which windows belong to which backdrop
screen and not let you copy files onto themselves or do other obscure
mind-altering things.  It just doesn't recognize the destination as a
workbench window.

So, what I want (both are *theoretically* simple):

1. UnloadWB
2. Only one LoadWB possible at a time per screen.

Doing #1 would make #2 not be such a bad problem, since you could remove
the useless extra copies.

PS:  Somebody gimme a second serial port!!

/\/\ /|  |    /||| /\|       | John M. Olsen, 1547 Jamestown Drive  /\/\
\/\/ \|()|\|\_ |||.\/|/)@|\_ | Salt Lake City, UT  84121-2051       \/\/
/\/\  |  u-jmolse%ug@cs.utah.edu or ...!utah-cs!utah-ug!u-jmolse    /\/\
\/\/             "A full mailbox is a happy mailbox"                \/\/