On November 13, 2002 15:25, Alexandre Julliard wrote:
But if we always use the DIB engine there won't be any coerce stuff at all, everything will be done directly in the DIB and we won't use the X11 renderer. Then the only time you have to copy is when doing a BitBlt to the screen.
The non-fully operational DIB engine issue aside (I believe Gav covered that).
I'm curious to know how you propose to hook the DIB engine in?.. I looked at several methods (changing the DC function table, for example) - none of them looked very appealing to us.
The other issue to be considered, is it neceesarilly incorrect to call it from the driver? Ove tells me that in Windows drivers are responsible for calling Windows' DIB engine. This is because a) its easier for the driver to know whats going to be faster, b) when the driver doesn't implement something itself it just passes it off to the DIB engine.
David