On 18 May 2018 at 16:08, Pablo Martin pmart-wine@riseup.net wrote:
This 3rd patch in the series is optional, it forwards the call as otherwise results in some duplicated code that can be avoided this way.
If you prefer to avoid the forwarding as hinted by Józef Kucia and keep direct calls from both CopySubresourceRegion methods you can just reject/ignore this patch.
In this particular case, I think the amount of duplicated code is small enough for it to be worth calling the wined3d function directly.
For more complicated cases, what you'd typically do would be to introduce a third function, e.g. d3d_copy_sub_resource_region() that handles the shared code, and forward both to that.