Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!uwm.edu!zaphod.mps.ohio-state.edu!mips!pacbell.com!pacbell!rtech!hoptoad!tim
From: tim@hoptoad.uucp (Tim Maroney)
Newsgroups: comp.sys.mac.programmer
Subject: Re: CLUT problem
Message-ID: <12230@hoptoad.uucp>
Date: 3 Sep 90 07:56:25 GMT
References: <20089@well.sf.ca.us>
Reply-To: tim@hoptoad.UUCP (Tim Maroney)
Organization: Electronics for Imaging, San Bruno CA
Lines: 22

I don't have an answer to this.  Neither, apparently, does anyone
else.  This has happened quite a few times lately with a number of
questions about color tables and such.  Couldn't Apple dispatch some
helpful soul who knows about Color Quickdraw to answer the many strange
questions that come up when using it?

For instance -- I'm drawing files (PICT and TIFF) into 32-bit offscreen
pixmaps, then drawing them to eight-bit screens.  The amount of color
distortion is phenomenal, although the files look great on a 32-bit
screen.  It's so bad that it seems the system is not even getting
mileage out of the 256 colors in the CLUT -- it seems to be making bad
selections.  What do I need to do?  Is there some magic color table bit
I should set?  Should I somehow increase the bits in the inverse table
for the monitor?  Should I draw back to a magic depth-zero offscreen
pixmap before dumping to the screen?  Does the unused byte of each
pixel have to have some particular value?  How can I get a handle on
what is causing the problem?
-- 
Tim Maroney, Mac Software Consultant, sun!hoptoad!tim, tim@toad.com

If you vote for clowns, you have no right to complain that only clowns
make it to the ballot.