From: Henri Verbeet <hverbeet@gmail.com>
Subject: Re: [PATCH 2/2] d2d1: Add ID2D1DeviceContext stub.
Message-Id: <CAOsNvwxReORvNuD2k1e-eGDXs3TqF7zUyTrETv=Y7FBS5Z1Eyg@mail.gmail.com>
Date: Sun, 3 Jun 2018 17:13:47 +0430
In-Reply-To: <CAG4Z_JL_e6_fL46Q1wOzv-=vxAZzNfm9+R2w0T6qkjCGqJW6Tw@mail.gmail.com>
References: <20180526064717.14023-1-nsivov@codeweavers.com> <20180526064717.14023-2-nsivov@codeweavers.com> <CAOsNvwxxT36iWpNCiY7zLSNeFp3HqhEqe30nDtOdMOoESgpRFg@mail.gmail.com> <CAG4Z_JL_e6_fL46Q1wOzv-=vxAZzNfm9+R2w0T6qkjCGqJW6Tw@mail.gmail.com>

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.