Path: utzoo!attcan!uunet!samsung!shadooby!mailrus!iuvax!watmath!watserv1!psych
From: psych@watserv1.waterloo.edu (R.Crispin - Psychology)
Newsgroups: comp.sys.mac.hypercard
Subject: Re: Memory loss when browsing
Message-ID: <159@watserv1.waterloo.edu>
Date: 17 Nov 89 13:46:19 GMT
References: <2663@client1.DRETOR.UUCP>
Reply-To: psych@watserv1.waterloo.edu (R.Crispin - Psychology)
Organization: U. of Waterloo, Ontario
Lines: 18

I get the same thing with a stack I am working on. It is a map of the 
building my office is in. Each office has a button on the floor plan.
If I access anyone of the 4 floor plans I end up with having around
52K of free space. When my stack closes it checks to see if their is
8K of free space and if so it compacts the stack. I have experimented 
with a few things to try and narrow things down. I discovered that by
putting the button scripts in the background script and just calling the
handler from the button I was able to reduce the free space from around
170K to the current 52K (there is about 450 buttons over 4 cards). It seems
that card buttons generate at least a 100 bytes of working space that is
not really needed in the stack. Unless I can find a solution I will change
my close stack script to look for 55K instead of 8K.
 
Richard Crispin
Dept. of Psychology             Bitnet: psych@watdcs 
University of Waterloo          Unix  : psych@watdcsu.UWaterloo.ca 
Waterloo, Ont.   Canada   N2L 3G1
(519)885-1211 ext 2879