On Thu, 4 Jan 2001, James Hatheway wrote:
> When I start my application (Groove) up with 16bpp mode,
> whatever is being bitblt'ed turns out as big black
> rectangles. If I start up with 8bpp mode, it looks fine.
> (or, at least as fine as it can look in 8bpp ^_^)
> If I comment out the small optomization, my app
> appears fine in 16bpp mode like it did in the past.
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)?
