Am Donnerstag, 23. August 2007 20:16 schrieb Jesse Allen: > On 8/23/07, Stefan Dösinger <[EMAIL PROTECTED]> wrote: > > Am Donnerstag, 23. August 2007 18:58 schrieb Jesse Allen: > > > Hi, > > > > > > I have my DIB driver code available on a public git host now: > > > http://repo.or.cz/w/wine/dibdrv.git > > > > > > I'm going to briefly describe it. > > > > Is your dib driver an all or nothing replacement of winex11 GDI drawing, > > or can it be mixed with winex11? > > I think it was decided not to mix the dc_funcs of the drivers. It > seems like it would be messy as you have to keep track of which > physDev goes where. So I decided to go all or nothing and have > replacements for at least every winex11 export to be safe. Forwarding > can be done as I described in the first email. I haven't tried yet, > since it is still pretty early. Some functions might not be needed, > though, like CreateDIBSection or CreateBitmap, but I still stubbed > everything so in testing anything that might show up will be easier to > identify. Ya, I've tried forwarding in wined3d, it is a pain. I've decided to drop that idea. What I meant was wether all GDI stuff happens in the new driver now, or if some windows/DIBs/whatevers can use the new code, and some the old.
> > How do you deal with BitBlt() or simmilar calls > > between your driver and winex11? > > I convert the bitmap to the destination device and proceed with the call. > See: > http://repo.or.cz/w/wine/dibdrv.git?a=commit;h=ad667f577e120ab96125c658679b >d4f8d2a2decc While you're at it, can you make it more universal so we can add a wined3d driver too, and convince AJ about it?