Jesse Allen ha scritto:
I'm trying to understand what the problem is to make you think there
needs to be a change. Are most of the problems with Blt related
functions?
No
It is my understanding the DIB engine should actually be able to call
the display driver and vice-versa. So I think we
On Tue, Apr 14, 2009 at 1:22 AM, Massimo Del Fedele wrote:
> The approach taken so far consisted in having 2 device pointers inside
> GDI32, one for dib engine and
> the other for normal display driver.
> This way had the disadvantage of having to keep in sync the DC with the
> right driver depend
Jesse Allen ha scritto:
What about other drivers? Is the DIB driver going to know how to
handle the others then?
The engine act as a filter between gdi32 and the DISPLAY driver, other stuffs
are untouched.
The changes on gdi32 are just to "prefere" the loading of the engine instead of
nor
"Massimo Del Fedele" wrote:
The approach taken so far consisted in having 2 device pointers inside GDI32,
one for dib engine and
the other for normal display driver.
Please don't post huge attachments to the mailing list in future,
post url for them instead.
--
Dmitry.
On Tue, Apr 14, 2009 at 1:22 AM, Massimo Del Fedele wrote:
> The approach taken so far consisted in having 2 device pointers inside
> GDI32, one for dib engine and
> the other for normal display driver.
> This way had the disadvantage of having to keep in sync the DC with the
> right driver depend
Reece Dunn ha scritto:
2009/4/14 Massimo Del Fedele :
The approach taken so far consisted in having 2 device pointers inside
GDI32, one for dib engine and
the other for normal display driver.
This way had the disadvantage of having to keep in sync the DC with the
right driver depending on
select
2009/4/14 Massimo Del Fedele :
> The approach taken so far consisted in having 2 device pointers inside
> GDI32, one for dib engine and
> the other for normal display driver.
> This way had the disadvantage of having to keep in sync the DC with the
> right driver depending on
> selected bitmap, whi
The approach taken so far consisted in having 2 device pointers inside GDI32,
one for dib engine and
the other for normal display driver.
This way had the disadvantage of having to keep in sync the DC with the right
driver depending on
selected bitmap, which lead to many small changes spread alo
