🚀 go-pugleaf

In article <4932@rosie.NeXT.COM> aozer@next.com (Ali Ozer) writes:
>In article <1992Sep3.090837.4884@cubetech.com> Andrew Loewenstern writes:
>>In article <1992Sep1.033025.7164@news.media.mit.edu> mike@media-lab.mit.edu writes:
>>> ... What I would like to do is simply get my hands on the pixel array
>>>that underlies the NXCachedImageRep of a grabbed frame,
>>>without copying and converting the whole frame.
>>Try to use either NXReadBitmap() or NXBitmapImageRep's
>>initData:fromRect: method (NeXT prefers NXBitmapImageRep).
>
>Arrg. I posted a longer reply to this question but I don't think it ever made
>it out. However, if you see another similar reply from me, apologies.
>
>As Andrew says, NeXT prefers NXBitmapImageRep. Under 3.0 reading images back
>from the window server has been speeded up, and you will see the most gain
>if you use the NXBitmapImageRep class. Under 3.0, all images come back as
>out-of-line messages (rather than as 64K buckets of bits, using "readimage").
>Also, under 3.0, it is possible for the images to come back "unpacked" (with
>non-standard bytes-per-row and bits-per-pixel values). This might seem like 
>a problem, but as long as you pay attention to the bytesPerRow and 
>bitsPerPixel params of the images, you will be fine.

Would it be possible for you or NeXTEdge to post a teeny bit of code
showing how to take advantage of the new image drawing speedups (such
as aligning the starting address, etc...)?  I think it would help all
of us out...


andrew
-- 
andrew@cubetech.com     | "We shall not cease from exploration
Andrew Loewenstern      |  And the end of our exploring
Cube Technologies, Inc. |  Will be to arrive where we started
                        |  And know the place for the first time." -T.S. Eliot