Thanks to Scott Rossi and Richard Gaskin for their suggestions, which led me to
the problem (large block of data stored as a custom property of a substack).
While poking around, I noticed that many but not most controls and groups, when
I get the customPropertySets of them, return the
On 4/30/2015 9:17 AM, dfepst...@comcast.net wrote:
While poking around, I noticed that many but not most controls and
groups, when I get the customPropertySets of them, return the value
cREVGeneral, although when I look for this in the property
inspector I do not find it. What causes this
Hi David,
Another issue could be a resource fork. If you're on a Mac and have
pasted a desktop icon into Finder's About box for the stack, that
pasted image becomes one or more resources in the resource fork. If you
delete the resources you don't want, stack bloat will decrease.
Here's a
An issue that has been discussed in the past might be unplaced groups --
groups that have been created at some time but aren't being used in the
stack. Here's one thread:
http://runtime-revolution.278305.n4.nabble.com/Storing-and-saving-a-settin
g-in-a-stand-alone-td4687858i40.html
Regards,
A stack I have gradually improved over several years now occupies 4 MB on disk,
whereas for a long time it was more like 500 KB.
Is there some way to diagnose what elements are causing this? I'd like to
generate a list of all of the stack's substacks, cards, fields, images,
scripts, etc., and
Thanks to Scott Rossi for calling my attention to “unplaced groups,” which seem
important enough to be better known. I found and purged a few of these, but
trimmed only a few KB off my 4.3 MB stack, which still seems much larger than
its (known) content can explain. Are there any other ways
Make a copy of your stack. If the copy contains multiple cards, delete
card by card (within reason) and check file size . If it's a single card
stack, delete object-by-object.
You say you went through unplaced groups, but you might also try deleting
everything in the stack, and seeing what the
David Epstein wrote:
... trimmed only a few KB off my 4.3 MB stack, which still seems
much larger than its (known) content can explain. Are there any
other ways of diagnosing what’s going on?
Look for things that can't be seen. :)
That is, if your stack was full of high-res graphics you'd
