Closed kg closed 1 year ago
This change looks good to me but I think we might want to make it slightly more generalized so that we can name other types of resources.
This change looks good to me but I think we might want to make it slightly more generalized so that we can name other types of resources.
I agree, but I'm not sure how we would go about it. I guess it would take a void* along with an enum specifying which type of FNA object we want to assign a name to?
For D3D all of the device child objects share a base interface that contains SetPrivateData, so the code there wouldn't need to change much. For vulkan I think we would just select the appropriate objectType, probably with a table.
I didn't implement tracing (yet?) because I'm not completely sure how to do it. I have an FNA change to go with this that I can make a PR for later