Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!rutgers!rochester!cornell!batcomputer!pyramid!prls!gardner
From: gardner@prls.UUCP (Robert Gardner)
Newsgroups: comp.sys.mac
Subject: Re: MultiFinder woes and joys
Message-ID: <7399@prls.UUCP>
Date: Fri, 13-Nov-87 16:09:17 EST
Article-I.D.: prls.7399
Posted: Fri Nov 13 16:09:17 1987
Date-Received: Sun, 15-Nov-87 11:00:10 EST
References: <256@stech.UUCP>
Reply-To: gardner@prls.UUCP (Robert Gardner)
Organization: Philips Research Labs, Sunnyvale, California
Lines: 20

In article <256@stech.UUCP> sysop@stech.UUCP (Jan Harrington) writes:
>	1. Occasionally, an application will quit unexpectedly (both MacWrite
>and FullPaint did this).  MultiFinder sends you a message that this has
>happened, but doesn't close the document that you were working on.  With
>MacWrite, it means that I have to reboot the machine to close the document
>so that I can work on it again (selecting Close from the Finder certainly
>doesn't help ...).

Anyone know why Apple chose this weird method of NOT closing files
automatically when an application quits? This has caused me more
headaches than I can imagine, especially during development if the
program crashes while a file is open. There doesn't seem to be
any way of explicitly closing the file without rebooting or trashing
the file (with option/command/whatever held down).

It looks like now there's an even more compelling reason for Apple
to change this. Would it break ANY existing code? Would it be that
hard? Resource files are closed automatically, so why not data files?

Robert Gardner