Recreate render target if EndDraw fails #1194
Comments
This was referenced Jan 24, 2017
Merged
This was referenced Mar 2, 2017
Merged
DHowett-MSFT
pushed a commit
that referenced
this issue
Mar 3, 2017
…2119) Direct2D can emit a failure or remove the backing hardware device from your render target at the end of any drawing operation. However, CoreGraphics does not natively have support for communicating failure states out to interested consumers. Enhanced Error Handling, when enabled, allows a sufficiently motivated developer to become part of CGContext's rendering lifecycle. The error of first and foremost importance is `D2DERR_RECREATE_TARGET`: It is not an error, but a plea to retry the last rendering operation after regenerating the render target. While CoreGraphics could batch up a list of pending drawing operations and replay them on a new target, it opts instead to report this to an Enhanced Error Handling consumer through `kCGContextErrorDeviceReset`. All other failing drawing operations result in `kCGContextErrorInvalidParameter`. In this pull request, **CALayer** has been augmented (in a bid to better prepare us for a hardware-accelerated future) to retry its rendering up to three (3) times if the device goes away. Since a layer can draw itself from start to finish, `-display` is the best point at which to handle the newly-minted CGContext errors. Fixes #1194.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is necessary before we switch CALayer to hw render target, so this doesn't block CGD2D merge to develop.
https://msdn.microsoft.com/en-us/library/windows/desktop/dd371766(v=vs.85).aspx,
The text was updated successfully, but these errors were encountered: