1. Replacing BmpCreate() by a home-made version that creates a more portable
version 2 bitmap on OS5 and Palm hi-res systems, and making sure this is the
bitmap that gets
cached (rather than the V3 conversion of it), fixes the problem. Using the
same home-made version of BmpCreate() also fixes the image optimization
problem.
2. I tried to save a step and directly generate a V3 bitmap, but that didn't
work--strangely, everything got scaled down by a factor of two.
3. There looks to me to be a bug in the image optimization code. The
optimized bitmap which is at a lower bit depth has the same color table as
the non-optimized bitmap. But this is surely wrong--the non-optimized
bitmap has a color table for a different depth. I don't know if bitmaps
with color tables ever get generated by the parser (do they?) but if they
do, then this will cause ugly color choices. Simple solution: Leave the
color table as NULL when calling BmpCreate() (or my home-made version of
it).
4. Question: Does the OS5 fullscreen table problem occur on lo-res OS5
systems? The answer determines where I am going to put the code for my
version of BmpCreate(). If the problem occurs there, then I will put the
code in screen.c, I suppose. Otherwise, I'll put it in hires.c.
Alex
--
Dr. Alexander R. Pruss
Department of Philosophy
Georgetown University
Washington, DC 20057-1133 U.S.A.
e-mail: [EMAIL PROTECTED]
online papers and home page: www.georgetown.edu/faculty/ap85
--------------------------------------------------------------------------
"Philosophiam discimus non ut tantum sciamus, sed ut boni efficiamur."
- Paul of Worczyn (1424)
_______________________________________________
plucker-dev mailing list
[EMAIL PROTECTED]
http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
