Set scene time through the Cesium frame port, in the application too

frame.setTime moves from the conformance renderer into the shared Cesium
ports, so the application's renderer has it. It moves the clock and asks for
a frame, which on-demand drawing needs. It no longer stops the clock: the
conformance renderer stops its own at creation, and the application's clock
keeps whatever state its owner gave it.
This commit is contained in:
Sameh Khamis committed 2026-11-06 17:38:29 -08:00
1 parent 338b75b8d8
commit 1a40c5a30a
5 files changed
+32 -16

No files matched your search

+4 -5
View File
@@ -7,11 +7,10 @@
* The renderer it makes is transitional. Its ports are the shared Cesium
* ports (`ports.js`), the ones the conformance renderer is checked with,
* less the members that would not be true of the application yet: the
* globe (it draws photoreal tiles the port does not know), `whenSettled`
* (it would not wait for them), `frame.setTime` (it would stop the
* application's clock). Those arrive with the layer families that need
* them (phase 2 of the renderer plan); `checkRendererShape` lists what is
* still missing.
* globe (it draws photoreal tiles the port does not know) and
* `whenSettled` (it would not wait for them). Those arrive with the layer
* families that need them (phase 2 of the renderer plan);
* `checkRendererShape` lists what is still missing.
* Until a family is ported, its code reaches the Cesium viewer through
* `cesiumViewerOf`, never through a renderer member, so no engine type
* crosses the contract and each call marks code still to port. Ported code