Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!snorkelwacker.mit.edu!shelby!neon!torrie
From: torrie@cs.stanford.edu (Evan J Torrie)
Newsgroups: comp.sys.amiga.advocacy
Subject: Re: How to improve Workbench 2.0!
Message-ID: <1991Feb2.230104.27338@Neon.Stanford.EDU>
Date: 2 Feb 91 23:01:04 GMT
References: <1991Jan27.105252.7019@marlin.jcu.edu.au> <7662@sugar.hackercorp.com> <56933@eerie.acsu.Buffalo.EDU> <1991Jan30.193443.5821@convex.com> <16243@sdcc6.ucsd.edu> <1991Feb2.184118.3880@ux1.cso.uiuc.edu>
Sender: torrie@Neon.Stanford.EDU (Evan James Torrie)
Organization: Computer Science Department, Stanford University
Lines: 23

ragg0270@uxa.cso.uiuc.edu (Richard Alan Gerber) writes:

>(2) The Mac trashcan sits on the desktop. From my observations, what
>must happen is something like this:
>When you drag a file to the Mac trashcan, the operating system somehow
>marks this file as having been put in the trash. It stays in that state
>until you chose "Empty Trash" from the desktop menu. But it's not quite
>that simple. Do you even notice how the trash gets emptied without your
>telling it to do so? Anytime there is disk activity on that disk, the
>trash gets emptied. Eject the disk. The trash is emptied. Write to the
>disk. The trash gets emptied. Bottom line: Put something in the Mac
>trashcan, you'll likely never get it back.

  This is yet another one of those things that has been changed in
System 7.0.  In 7.0, the Mac trashcan is termed a container, just like
any other disk.  It keeps files until you explicitly empty it... I
believe this works across reboots, although I have yet to work with
System 7.0 - simply reading from pre-release information.
  
-- 
------------------------------------------------------------------------------
Evan Torrie.  Stanford University, Class of 199?       torrie@cs.stanford.edu   
Fame, fame, fame...  What's it good for?  Ab-so-lute-ly nothing