On Mon, 18 Jan 2021 at 13:58, Rémi Bernon rbernon@codeweavers.com wrote:
The idea here is only to have a minimal implementation of SwapDeviceContextState, to fix the D2D1 over D3D11 regression. What's missing is the actual state change, as well as the enabling / disabling or the D3D10 / D3D11 interface methods when state is changed to another version, as described in [1].
I didn't really investigate what the full device context state implementation would require, but I suspect it to be much bigger scope. This could possibly serve as an initial work for it as well.
That makes it a fair bit harder to judge whether this is really the right way to go, of course. My expectation would be that implementing state save/restore would only be marginally more complicated than the current d3d10 stateblock implementation.