On 6/16/22 05:01, Henri Verbeet wrote:
On Wed, 15 Jun 2022 at 20:09, Zebediah Figura zfigura@codeweavers.com wrote:
One thing we could probably do in general is make it possible to delay setting the parent ops, e.g. set it as wined3d_null_parent_ops initially and then add a separate function like wined3d_resource_set_parent_ops() once the client object is fully initialized.
Right, that probably makes sense, although the implications for objects currently referenced by the command stream probably deserve a look.
Hmm, I don't see what you mean? Since the only parent op is currently the destruction callback, it can't be called until all references have been dropped, and it'd definitely be an error to call wined3d_resource_set_parent_ops() without holding a reference to the resource.