> Hmm. In theory, it shouldn't make much of a difference for DIB depths
> above 8bpp. Both the optimized and unoptimized code paths goes through
> X11DRV_DIB_DoCopyDIBSection (albeit with differing arguments), provided
> the blit isn't clipped away on the way. What is the destination of the
> failing blit? What do you mean by "start up with 8bpp mode"? Is the source
> bitmap perhaps always 8bpp, even if you run at 16bpp? Does the blit
> encompass the whole bitmap, or only part of it? Is the source bitmap an
> "upside-down" one (positive DIB height)?
Hi Ove,
When I said "8bpp mode", I meant running X in 8bpp. Sorry
for the confusion. So, when I run X in 8bpp, there is no corruption,
however when I run X in 16bpp there is corruption. I will answer
your other questions later today, I'm concentrating on another
bug at the moment.
Thanks,
-James
--
James Hatheway
Software Designer - Macadamian Technologies, Inc.
[EMAIL PROTECTED] ~ http://www.macadamian.com
"Nothing is a problem once you debug the code."
