22 Jul
2007
22 Jul
'07
11:23 a.m.
Hi all and Magnus,
Magnus Olsen wrote:
Hi
what I can see metafile are done in two place in windows one in win32k
another in gdi32
some stuff can only be done in win32k in windows and reactos and metafile
need some setup
in win32k for it exists kernel api that need it.
EnhMeta (not 16 bit) look at my code example, it's a DC with the EnhMeta bits set in
the handle table, most of the work is done in gdi32. Wine again is a good example.
Meta (16 bit) is created in gdi32,,,,, but,,,,, the dc handle is created via
nt create object. It works out side the normal DC mode of thinking.
Still, just like wine does it,,,,,, it is all handled in gdi32 not win32k, looks
like a gdi32 script player.
Yes our gdi32 and win32k sucks it should be good a
good rewriting was done,
for gdi subsystem. But before we can do that we need real testcase for each
NtGdi* stuff and test it in windows so we really known how they works.
after that is done we can start rewrite each NtGdi*. then later testcase for
each Gdi* api in gdi32, that will make our gdi substem good. and stable
Already done. Wine test with hooks can reveal the truth. Also there is nothing
wrong with that at all.
But we need share memory betwin win32k and gdi/dx
stuff
I have ideas to fix this. Blame GvG for this one!
I known the metafile implement is not 100% ok,
it is base how wine doing it, and I did follow wine implement
and did not check how it really works in windows nt,
It's okay.
Thank you for your cooperation,
James