route-graphics 1.44.4 → 1.45.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +19 -0
- package/dist/RouteGraphics.js +92 -92
- package/dist/cli/routeGraphicsCli.js +13 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -83,6 +83,25 @@ either backend.
|
|
|
83
83
|
`createAssetBufferManager()` may keep image and video assets as direct source
|
|
84
84
|
URLs when possible, while audio and font assets remain buffer-backed.
|
|
85
85
|
|
|
86
|
+
`render()` remains synchronous, but plugins may mount asynchronously. Before
|
|
87
|
+
extracting pixels or reading a mounted layout, await the requested scene:
|
|
88
|
+
|
|
89
|
+
```javascript
|
|
90
|
+
app.render(nextState);
|
|
91
|
+
await app.whenRenderReady();
|
|
92
|
+
const image = await app.extractBase64();
|
|
93
|
+
```
|
|
94
|
+
|
|
95
|
+
This waits for async element operations and their first renderer submission,
|
|
96
|
+
not the end of animations/reveals, a GPU fence or browser composition. Identical
|
|
97
|
+
renders share the current wait. Supersession or destruction before readiness
|
|
98
|
+
rejects with `AbortError`; preparation/render errors reject with their original
|
|
99
|
+
error. Before any render and after destruction there is no active wait. Capture
|
|
100
|
+
the promise before requesting another state to observe that particular request.
|
|
101
|
+
Use `renderComplete` when playback completion is required. The PNG CLI waits
|
|
102
|
+
for scene readiness before applying `--time`; `--wait-for-render-complete`
|
|
103
|
+
retains its separate playback-completion meaning.
|
|
104
|
+
|
|
86
105
|
Assets loaded by an app instance can be released after no rendered or
|
|
87
106
|
transitioning element still references them:
|
|
88
107
|
|