Feb. 11, 2012
1:17 a.m.
Schwab,Wilhelm K wrote:
Stef,
I have an idea for something that might be simple enough to make the point. It is confusing though, especially that once an image goes bad, it stays bad, even though (AFAIK, I don't save it after the damage is done). For certainty, you could monitor file timestamps or in the extreme compare md5 checksums on the image at various points. Perhaps the first thing after unzippping a new image add 'self halt' at the top of SmalltalkImage>>snapshot:andQuit: This might help hunt down anything that is forcing an image save without your consent.
cheers, -ben