🚀 go-pugleaf

In article <7399@prls.UUCP> gardner@prls.UUCP (Robert Gardner) writes:
>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).
	Actually, there is a way.  Get a copy of the Developer's Tools
desk accessory, along with all the normal file copy/delete/information
routines it also allows you to close an arbitrary file.  I added it to
the DA (long before I joined Apple) for just this reason.

	For those of you with a more technical bent the way DevTools
closes arbitrary files is to do a GetFileInfo (which returns a refNum
if the file is open) and then close the returned refNum.

	You do have to be careful with what files you close though :-)

	Dev. Tools (aka Developer's Tools) should be available on your
local info-mac server.  If you can't find it let me know (VIA MAIL, not
a posting) and I'll send you a copy, or demand justifiing it, repost
it again.  BTW, version 2.2 is current and has been for quite some
time.
-- 
	David W. Berry
	dwb@well.uucp                   dwb@Delphi
	dwb@apple.com                   973-5168@408.MaBell
Disclaimer: Apple doesn't even know I have an opinion and certainly
	wouldn't want if they did.