🚀 go-pugleaf

In article <734@mit-amt.MEDIA.MIT.EDU> mjkobb@media-lab.media.mit.edu (Michael J Kobb) writes:
>a piece of software.  The software I chose to do this was SuperPaint.  I own
>1.0, which has always worked fine for me, but I was able to borrow 2.0 from
>[...]
>Anyway, I started work on the dialogs, and much to my dismay, as they became
>more complicated (in the object layer), the software would crash while saving.
>This not only wiped out the changes since the last save, but it KILLED MY
>SAVED FILE, too.  Needless to say, I was a bit peeved.  This happened on both
>a MacPlus (2.5MB RAM, trillions of inits, MF 6.1b7, 128k Ram Cache, Sys 6.0.2),
>the same Plus under just Finder with no cache, and on a Mac II with tons of
>memory and almost no inits (basically, Pyro).

  SuperPaint 2.0's 'PICT' format doesn't seem to be quite standard. I also
experienced quite a few crashes-while-saving, usually with files that had
a number of grouped objects in the Draw layer (between 20 and 50 individual
objects). Sometimes the file would appear fine, then when it was re-opened
later, the sizes and positions of the objects would be radically distorted,
both with respect to the page and to each other. This happened under
conditions identical to Michael's, except I was running System 6.0.3.

  Needless to say, I don't use SuperPaint 2.0. Are other people experiencing
similar crashes? I haven't heard anything on the net to indicate this is a
quality-assurance blowit of Word 3 proportions, although if our experience
is typical, it would sure seem that way!


-- 
==========     .......     =============================================
Ken McLeod    :.     .:    UUCP: ...{spsd,zardoz,felix}!dhw68k!thecloud
==========   :::.. ..:::   INTERNET: thecloud@dhw68k.cts.com
                ////       =============================================