fix(time): latch the Cesium clock at creation; document the clock's limits

Review of Tasks 0–1:
- The Cesium engine clock attaches its frame latch to viewer.clock.onTick
  when the engine is created, so it runs before onTick listeners added
  later (cameraVerbs installs its own after the engine exists). Before, it
  attached on first use and would have run after them. A viewer without a
  clock still latches lazily on the scene's preUpdate.
- GlobeClock lists what is not on the app clock yet: Cesium's viewer clock
  (its lighting and property reads at currentTime), the launch replay
  timeline and the mission orbit's GMST frame (Task 15a), the satellite
  cloud's SGP4 and orbit bake (Task 14a), and wall-clock throttles. The
  plan's T14a/T15a now carry those moves.
- freeze/offset/rate change now() at once and frameTime() from the next
  frame; QA helpers request a render after moving the clock.
This commit is contained in:
German Khokhlov committed 2026-10-16 16:18:08 +04:00
1 parent 7c7422e281
commit f7f4e9a45c
5 files changed
+43 -10

No files matched your search

+3 -1
View File
@@ -22,7 +22,9 @@ function finite(value, label) {
* @property {() => number} beginFrame Latches and returns the frame time; the
* globe engine calls it once at the start of each of its frames.
* @property {(ms?: number) => void} freeze Holds the time at `ms` (default:
* the current time). QA and tests only.
* the current time). QA and tests only. Like offset and rate, it changes
* now() at once and frameTime() from the next beginFrame (the engine's
* next frame); request a render after it in request-render mode.
* @property {() => void} resume Runs on from the frozen time.
* @property {(ms: number) => void} offset Sets the time to the wall clock
* plus `ms`, running on from it at the current rate (it ends a freeze).