From: Nikolay Sivov Subject: Re: [PATCH 2/2] d2d1: Add ID2D1DeviceContext stub. Message-Id: Date: Sun, 3 Jun 2018 22:55:07 +0200 In-Reply-To: References: <20180526064717.14023-1-nsivov@codeweavers.com> <20180526064717.14023-2-nsivov@codeweavers.com> On Sun, 3 Jun 2018 at 14:43, Henri Verbeet wrote: > On 29 May 2018 at 22:09, Nikolay Sivov 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. >


On Sun, 3 Jun 2018 at 14:43, Henri Verbeet <hverbeet@gmail.com> wrote:
On 29 May 2018 at 22:09, Nikolay Sivov <bunglehead@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.