Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!spool.mu.edu!agate!ucbvax!mtxinu!sybase!mercury!eallen
From: eallen@mercury.sybase.com (Ed Allen)
Newsgroups: comp.sys.mac.hypercard
Subject: Re: HC on a Network.  QUESTIONS & HELP PLEASE
Message-ID: <12940@sybase.sybase.com>
Date: 23 May 91 17:11:33 GMT
Article-I.D.: sybase.12940
References: <1991May22.232930.3318@fennel.cc.uwa.oz.au>
Sender: news@Sybase.COM
Reply-To: eallen@mercury.UUCP (Ed Allen)
Organization: Sybase, Inc.
Lines: 20


HyperCard does a lot of disk access because of the auto-save. Run a stack
with an icon animation and you'll see the disk access each time it changes
the icon of the button to save the new icon. If your button has this kind
of effect it will access disk, I think it does so for Hiliting the button,
and a bunch of other things where you wouldn't expect it a priori.

HyperTemp 1 is the new file created when you compact a stack.  Normally,
the compact operation goes to completion, the old stack gets deleted, and
HyperTemp1 gets renamed with the stack name.  If you do a compact operation
while running on a big monitor with the finder window showing the stack
visible under multifinder, you will see this operation.  This is also the
reason the stack jumps around in the finder when you look for it after
compacting.

**** NOTE to HyperCard Team**** It would be really nice if you can have the
compacted stack put into the same place in the finder window for the folder
that the original stack was.  It's annoying to always be reorganizing icons.

Ed Allen eallen@sybase.com