Path: utzoo!attcan!utgpu!watmath!iuvax!rutgers!mcnc!kk
From: kk@mcnc.org (Krzysztof Kozminski)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Meaning of visRgn in offscreen bitmaps + whinings about PrintManager.
Message-ID: <1346@speedy.mcnc.org>
Date: 23 Aug 89 13:26:40 GMT
References: <22321@andante.UUCP> <30755@ucbvax.BERKELEY.EDU> <34168@apple.Apple.COM> <1336@speedy.mcnc.org> <3733@internal.Apple.COM> <1342@speedy.mcnc.org> <3801@internal.Apple.COM>
Reply-To: kk@mcnc.org.UUCP (Krzysztof Kozminski)
Organization: Microelectronics Center of NC; RTP, NC
Lines: 42

In article <3801@internal.Apple.COM> parent@apple.com (Sean Parent) writes:
>In article <1342@speedy.mcnc.org> kk@mcnc.org (Krzysztof Kozminski) writes:
>> [bitching about sloooooooooow printing of bitmaps on LW]
>
>I believe that the ratios are odd because of the overhead involved in 
>scalling the image.

Yes, but the scaling is the simplest possible when 'exact bimap image' is
turned ON: 1 pixel of image maps into 4x4, 2x2 and 1x1 at the 100%, 50%, 25%.
Why isn't there a CASE in the LW driver to handle these special values
efficiently? (BTW, 100% with 'exact bimap image' turned OFF takes ~10 times
longer than with ON - this I can easily understand).

>BitMaps are slow because they are sent as Hex data as required by PostScript.

I've just looked it up in the Adobe manuals: Hex or binary turns out to be
the same bits (unless LW driver tries to do some fancy data compression
while sending it over).

The way I figure it out, it should take about 3 seconds to print a full-page
bitmap at 25% reduction with 'exact bimap image' turned ON. (this is assuming
transfer rate about .5Mbytes per second - I seem to recall this value from
somewhere in the IM).  Can anybody tell me why it ain't so?

>> [more bitching from KK about castrated QuickDraw for LaserWriter]
>PostScript does not have the concept of transfer modes.

Yes, perhaps I should be more specific: how come 'srcOr' is supported
(the only mode not supported for bit image transfer is 'srcXor') and
'patOr' is not? For a while I had a little routine that implemented
'patOr' for 'PaintRect' by filling a small 16x16 bitmap with the
desired pattern, and then repeatedly doing CopyBits from it to cover
the destination rectangle, while taking care of the proper alignment as
well.  Before even getting this to work, I've found out that doing my
own entire image and copying it over is faster.  Now what is so
complicated about the above that it could not be implemented by Apple
in the first place?

KK
-- 
Kris Kozminski   kk@mcnc.org
"The party was a masquerade; the guests were all wearing their faces."