Skip to content

Explainer: Swap Chain #1618

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.

Sign up for GitHub

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

Merged
kvark merged 3 commits into from
Apr 13, 2021
Merged

Explainer: Swap Chain #1618

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
17bb048
Explainer: Swap Chain
kainino0x Apr 9, 2021
804162e
decoupling
kainino0x Apr 9, 2021
c222d1f
zero or more
kainino0x Apr 12, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
decoupling
  • Loading branch information
@kainino0x
kainino0x committed Apr 9, 2021
commit 804162eb9b0f3a724512fedf2977fc124675b536
6 changes: 6 additions & 0 deletions explainer/index.bs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -735,6 +735,12 @@ Following this, WebGPU has no "default" drawing buffer.
Instead, a WebGPU device may be connected to *arbitrarily many* canvases (via
`GPUCanvasContext`s) and render to all of them.
Comment thread
kainino0x marked this conversation as resolved.
Outdated

Canvas context creation and WebGPU device creation are decoupled.
Any `GPUCanvasContext` may be dynamically used with any `GPUDevice`.
This makes device switches easy (e.g. after recovering from a device loss).
(In comparison, WebGL context restoration is done on the same `WebGLRenderingContext` object,
even though context state does not persist across loss/restoration.)

In order to access a canvas, an app gets a `GPUTexture` from the `GPUCanvasContext`
and then writes to it, as it would with a normal `GPUTexture`.

Expand Down