-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Questions for WGPUSurface #295
Comments
Thank, closing in favor of these. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Should a
WGPUTextureUsage
be added toWGPUSurfaceCapabilities
with guarantees likeRENDER_ATTACHMENT|TEXTURE_BINDING|COPY_SRC|COPY_DST
?Where do errors go when there is no configured device on the surface? When exactly does that configure device change (unconfigure, failed calls to configure when there is already a configured device, etc). Are failures reflected in a status enum for things not linked to a device?
Is the following defined to always work without additional waits? At least on Vulkan and D3D12 it will require waiting for the GPU on WGPUSurfaceRelease:
What do we do with the extensibility and the status of GetCurrentTexture? How do we notify that a surface has been lost?
The text was updated successfully, but these errors were encountered: