You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: samples/DrawingBackendBenchmark/README.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,7 +15,7 @@ Depending on what the machine can initialize, the sample can show:
15
15
-`SkiaSharp (GPU)`: Skia using a GPU-backed `GRContext` when the hidden GL host is available
16
16
-`WebGPU`: the offscreen `ImageSharp.Drawing.WebGPU` backend
17
17
18
-
The sample always starts with the CPU and Skia CPU paths. The WebGPU backend is added only when `WebGPUEnvironment.TryProbeComputePipelineSupport(...)`succeeds. The Skia GPU backend is added once the hidden `SKGLControl` has produced a usable `GRContext`.
18
+
The sample always starts with the CPU and Skia CPU paths. The WebGPU backend is added only when `WebGPUEnvironment.ProbeComputePipelineSupport()`returns `WebGPUEnvironmentError.Success`. The Skia GPU backend is added once the hidden `SKGLControl` has produced a usable `GRContext`.
19
19
20
20
## What the UI shows
21
21
@@ -77,7 +77,7 @@ This keeps the benchmark focused on scene rendering rather than repeated target
77
77
78
78
The WebGPU backend is intentionally small:
79
79
80
-
- it probes support up front with `WebGPUEnvironment.TryProbeComputePipelineSupport(...)`
80
+
- it probes support up front with `WebGPUEnvironment.ProbeComputePipelineSupport()`
81
81
- it renders into an owned offscreen `WebGPURenderTarget<Bgra32>`
82
82
- it draws through `CreateCanvas(...)`, not a hybrid CPU plus GPU canvas
83
83
- it reads back the final frame only when the UI requests the last-iteration preview
Copy file name to clipboardExpand all lines: src/ImageSharp.Drawing.WebGPU/WEBGPU_BACKEND.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,8 +28,8 @@ Those types all exist to get a `DrawingCanvas<TPixel>` over a native WebGPU targ
28
28
29
29
The support probes also live outside the backend:
30
30
31
-
-`WebGPUEnvironment.TryProbeAvailability(...)` checks whether the library-managed WebGPU device and queue can be acquired
32
-
-`WebGPUEnvironment.TryProbeComputePipelineSupport(...)` runs the crash-isolated trivial compute-pipeline probe
31
+
-`WebGPUEnvironment.ProbeAvailability()` checks whether the library-managed WebGPU device and queue can be acquired
32
+
-`WebGPUEnvironment.ProbeComputePipelineSupport()` runs the crash-isolated trivial compute-pipeline probe
33
33
34
34
That split keeps support probing separate from flush execution. `WebGPUDrawingBackend` is the flush executor, not the public support API. The WebGPU constructors create their objects directly; callers use `WebGPUEnvironment` when they want explicit preflight checks.
0 commit comments