gmurray81
commented
3 years ago BTW, I think
GrContext::abandoned()would help with #1573 and #1642
since I didn't see a SkiaSharp level way to tell if another SKSwapChainPanel had abandonded the resources for a GrContext. But I'm not sure the current abandon behavior is appropriate anyhow?
Description
SkCamera.h and SkMatrix44.h are DEPRECATED. Use SkM44 if you want to have 3d transformations.
GrContext::createBackendTexture functions that initialize the texture no longer guarantee that all the data has been uploaded and the gpu is done with the texture. Instead the client can assume the upload work has been submitted to the gpu and they must wait for that work to finish before deleting the texture. This can be done via their own synchronization or by passing in a finish proc into the create calls which will be called when it is safe to delete the texture (at least in terms of work done during the create). https://review.skia.org/286517
Add api on GrContext, updateBackendTexture that will upload new data to a GrBackendTexture. https://review.skia.org/288909
Added GrContext::oomed() which reports whether Skia has seen a GL_OUT_OF_MEMORY error from Open GL [ES] or VK_ERROR_OUTOF*_MEMORY from Vulkan. https://review.skia.org/298216
GrContext::abandoned()