Merge branch 'main' into fix/cockpit-subject-camera-hud

This commit is contained in:
German Khokhlov authored and GitHub committed 2026-11-19 01:08:29 +04:00
commit 0fdfc3cf45
761 files changed
+3492 -90

No files matched your search

+22 -12
View File
@@ -2820,10 +2820,11 @@ good words, at first those checked when the provider was registered.
The Rail layer offers a read API for such a view: `getSelectedTrain()` and
`getCockpitSubject()` (a snapshot of the train: where it is along its line,
which way it runs (`pathBinding.js` learns it), its rail height, speed as
reported or derived, position source, feed credit and stops, and
`selectedAtMs`, when the user last selected it by a click or `focusTrain`,
even again; null after a deselection and for a train only a hold selected),
which way it runs (`pathBinding.js` learns it), its rail height (null while
no floor is known), speed as reported or derived, position source, feed
credit and stops, and `selectedAtMs`, when the user last selected it by a
click or `focusTrain`, even again; null after a deselection and for a train
only a hold selected),
`setCockpitSubject(key)` (its marker, 3D model and card hidden, the selection kept, its
feed held, clicks and Escape left to the view; the held copy stays the one
drawn of its train while held, another feed's copy hidden, and it keeps
@@ -2836,14 +2837,23 @@ offers the same for a vehicle (`getSelectedVehicle`, `getCockpitSubject`,
`setCockpitSubject`, `focusVehicle`): a held vehicle keeps playing when it is
out of the camera's view, and its sprite, 3D model, card, trail and detection
box are hidden; released, it is out of play until a visibility sweep finds it in
view. Its snapshot's `position.groundHeightM` is the floor where playback draws
it (the drawn marker's height while it is placed, else its segment's two
reports' floors at the playback fraction), not the newest report's, and null while that floor is unknown. Rail's `path.direction` is the
way the drawn train runs: once playback has placed it, a report that runs back
turns it only when playback reaches that report. `docs/APPLICATION.md` (Cockpit subjects) shows a minimal provider. `src/ui/cockpitSubjectView.test.mjs`,
`src/cockpitSubjectProviders.test.mjs`, `src/cockpitProgress.test.mjs`,
`src/layers/rail/cockpitSubject.test.mjs` and the Transit lifecycle tests
cover them.
view. Turning the layer off ends the hold. Its snapshot's
`position.groundHeightM` is the floor where playback draws it (the drawn
marker's height while it is placed, else its segment's two reports' floors at
the playback fraction), not the newest report's, and null while either of
those two floors is unknown. Rail's `path.direction` is the way the drawn
train runs: once playback has told its direction, a report that runs back
turns it only when playback starts the segment to that report. A train turns
once it is more than a standing train's GPS jitter back from the last place a
longer move took it, however slowly it backs, so jitter on either side of
where it stands keeps its direction, and so does playback's jump to a
corrected position (a break, or a new clock epoch). While movement gives no
direction, the snapshot uses the operator's last reported bearing.
`docs/APPLICATION.md` (Cockpit subjects) shows a minimal provider.
`src/ui/cockpitSubjectView.test.mjs`, `src/cockpitSubjectProviders.test.mjs`,
`src/cockpitProgress.test.mjs`, `src/layers/rail/cockpitSubject.test.mjs`,
`src/layers/rail/pathBinding.test.mjs` and the Transit lifecycle tests cover
them.
## Context coordination