[PATCH 2/2] d2d1: Add ID2D1DeviceContext stub.

Nikolay Sivov bunglehead at gmail.com
Sun Jun 3 15:55:07 CDT 2018


On Sun, 3 Jun 2018 at 14:43, Henri Verbeet <hverbeet at gmail.com> wrote:

> On 29 May 2018 at 22:09, Nikolay Sivov <bunglehead at gmail.com> wrote:
> > Context can render in two ways - populating command list, or rendering
> to a
> > bitmap object. I was thinking we should create a dxgi target when
> rendering
> > to a bitmap and forward calls to it. For command lists we don’t need to
> > create a real target.
> >
> Yeah, but I think we'd still like things to work in essentially the
> same way. When rendering to a command list, we'd record commands for
> later execution. When rendering to a surface we'd do the same, but
> also start execution (more or less) immediately, potentially on a
> different thread.


Does that imply moving d3d target to such model first? It also looks like a
way to make Flush() do something.


>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.winehq.org/pipermail/wine-devel/attachments/20180603/d38067ef/attachment.html>


More information about the wine-devel mailing list