Article View: comp.sys.mac
Article #5523Re: SuperPaint 2.0
From: Mark Frost
Date: Fri, 29 Sep 1989 03:59
Date: Fri, 29 Sep 1989 03:59
44 lines
2902 bytes
2902 bytes
In article <115028@felix.UUCP> kehr@felix.UUCP (Shirley Kehr) writes:
>In article <26695@dhw68k.cts.com> thecloud@dhw68k.cts.com (Ken McLeod) writes:
>I don't have the crashes, but there are other problems with SuperPaint
>drawings in Word 4.0. Don't even think of taking a SuperPaint drawing
>from Word 4.0 back to SuperPaint to change it. (I know, there is supposed
>to be some kind of linking between the two, but I just haven't explored
>that feature yet.)
>
>When you get the drawing (from Word 4.0) into SuperPaint, even though it
>had been grouped, the pieces are now widely scattered. When you ungroup
>it to work on it, you may find some of the pieces missing until you assign
>a larger drawing size. If you haven't given SuperPaint more than its default
>700K to work with, you can't even do that.
Weird. I was working on a project with lots of little pictures. I started
drawing the small internals of the picture, rotating as necessary, grouping
those smaller objects into bigger objects, working on those and
finally grouping the little objects (no more than 20) into one large object.
Then if say, I quite the application and came back in, there seemed to be about
a 40% chance the my object(s) would be corrupted. Corrupted in the sense that
the smaller objects that were now grouped into the larger object had drifted
apart a pixel or two (and essentially looked like crap now). I then needed
to ungroup several times until I had ungrouped all the objects and "sub-objects"
in the now screwed up object in order to fix the thing. If I left the screwed
up object(s) alone, it was also possible that it ("object drift") would happen
again messing up my object even furthur.
All in all, for a 30-hour project, I spent probably 8 hours correcting
the objects after SuperPaint 2.0 screwed them up. Unfortunately, since I
had already invested so much time with it, I didn't have anything else,
and I had a deadline, I stuck with SuperPaint.
I had this problem on an SE/20 and a IICX. Needless to say, I will
never use SuperPaint 2.0 again.
Mark Frost
Office of the the Computing Coordinator
Humanities Division
University of California at Santa Cruz
Santa Cruz, California 95064
(408) 459-4603
Internet: humtech@ucschu.UCSC.EDU
Bitnet: humtech@ucschu.bitnet
Uucp: ...!ucbvax!ucscc!ucschu!humtech
Technical Details
Message-ID:
<9265@saturn.ucsc.edu>Path:
arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!agate!saturn!ucschu.UCSC.EDU!humtechReferences:
<734@mit-amt.MEDIA.MIT.EDU> <26695@dhw68k.cts.com> <115028@felix.UUCP>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!agate!saturn!ucschu.UCSC.EDU!humtech From: humtech@ucschu.UCSC.EDU (Mark Frost) Newsgroups: comp.sys.mac Subject: Re: SuperPaint 2.0 Keywords: What the... Message-ID: <9265@saturn.ucsc.edu> Date: 29 Sep 89 03:59:54 GMT References: <734@mit-amt.MEDIA.MIT.EDU> <26695@dhw68k.cts.com> <115028@felix.UUCP> Sender: usenet@saturn.ucsc.edu Reply-To: humtech@ucschu.UCSC.EDU.UUCP (Mark Frost) Organization: Humanities Division, UC Santa Cruz Lines: 44