- Following comes only from the camera's own follow, never claimed ahead
of it; vessels, which the camera does not follow, are flown to.
- A drag or a long press never selects, and only a clean click on open map
closes the card; a card painted on the overlay is not open map.
- Closing the card lets go through its own layer only, as the person's
action, leaving other layers' selections alone.
- Radio's panel, with its local SDR tuner, shows whether or not the Radio
layer is on; Contacts' Cockpit entry hides only while the card offers its
own.
- Expanded Context keeps the credits beside it right to left and with the
minimal HUD.
- Context counts as closed until its panel says it is open; closed, the
card's refresh and the view reading pause, and opening reads the view.
- The five-minute re-read fetches again past the caches, keeps what is
shown meanwhile, and an empty brief is not kept.
Co-authored-by: Manjunath Paparaju <[email protected]>
Context no longer reaches into Cesium or the viewer: the view it describes
comes from the camera port (pose, view rectangle, moveEnd and changed), a
fly-to goes through flyToBounds, and clicks come from the input dispatcher,
which picks each click once for every layer and skips it while a tool holds
the pointer. The card says Following while the camera follows its own item,
as the follow's key names it (src/data/followed.js), whoever started the
follow.
Co-authored-by: Manjunath Paparaju <[email protected]>
- Closed, the panel mounts neither the card nor the view summary, so it
reads no layer records and fetches nothing.
- The weather and news brief goes through the app's regional service
(endpoint overrides, lifetime signal), and a failed read is not kept.
- A spot that stays put reads its brief and hazards again every five
minutes; turning FIRMS on or off updates the hazards at once.
- Enter Cockpit is offered only for layers the tracking action can follow
(not local ADS-B), and a failed attempt leaves the card as it is; a
satellite ride gives up when the card changes or Context goes away.
- Closing the card lets go of the camera when it follows the card's item.
- Map picks leave Context alone while Cockpit runs.
- Expanded Context sits on the left edge in right-to-left languages, lets
go on the phone layout or in Cockpit, and a remount starts collapsed
without leftover tab classes.
- The Inspector and Properties tabs have tab ids, panels and arrow keys.
- Town lookups run again after zooming back in, the camera preview shows
facts only for its own camera, route places wait for the same route, and
acres and heights use the app's number format.
- The omnibar gets no runner from a voice session already disposed.
Co-authored-by: Manjunath Paparaju <[email protected]>
While a layer they act on is on, the Visual panel's detection overlay and
3D aircraft controls move into their tab in Context, beside what they
affect; Cockpit still takes them first, and they go back to Visual when the
layer goes off.
Co-authored-by: Sameh Khamis <[email protected]>
The Context panel's main tab shows the mode row again, with Contacts
(nearby sites search, the TR-3B toggle and the Awareness list) and Space
Missions (the roster and launch replay); only the Properties tab hides
them. Radio shows while its layer is on, and turning Radio or Launches on
opens Context. When Contacts follows the aircraft the card shows, its list
sits inside the card in a compact form and the card leaves out the flights
and vessels Contacts already lists. The card's Enter Cockpit replaces the
Contacts button, and leaving the cockpit returns focus to it.
Co-authored-by: Sameh Khamis <[email protected]>
Tracking set by another control or by voice for another craft no longer
shows Following on the open card: the card remembers the entity its own
pick started tracking, and any other tracked entity clears Following.
Co-authored-by: Manjunath Paparaju <[email protected]>
A share link or restored view moves the camera without a moveEnd, and the
once-a-second read of camera changes dropped the last one, so Context named
a point from the fly-in. A last read now follows the final change.
Co-authored-by: Manjunath Paparaju <[email protected]>
FIRMS needs a key the browser cannot see. Without one the proxy answers
503, so Context no longer asks for fire hits unless the FIRMS layer is on.
Co-authored-by: Manjunath Paparaju <[email protected]>
Expanded, Context covers the right edge from top to bottom, so the credit
row now ends short of it. The credit model knows the expanded column and
pins the gap, the header test lists the new search and expand buttons, and
the controls tolerate operations without an annotation resolver.
Co-authored-by: Manjunath Paparaju <[email protected]>
The shell passes the ground picker to the click bridge, so the UI shell no
longer pulls in the annotation and search stack. Context's new modules are
owned by the packages that import them and formatted with the rest.
Co-authored-by: Manjunath Paparaju <[email protected]>
The shell connects the layer store that Context and the omnibar share,
installs the click-to-Context bridge and removes both on dispose. Voice
sessions hand their command runner to the same store, and the stylesheet
imports the Context styles.
Co-authored-by: Sameh Khamis <[email protected]>
A transit vehicle picked on the map now finds its record in Context (the
click carries the feed and vehicle key), so the card shows its operator,
place, route, report age and the operator's last reported state in plain
words. The layer card breaks transit in view down by motion (moving,
stopped, waiting for an update, no recent fix), mode, operator, last
reported state and crowding where the feed has it; vehicle-position feeds
carry no timetable, so early or late is not shown. Rows in the in-view
list carry a motion icon.
- Context reads what is under the pointer when the button goes down. The
flights layer acts on the click first and swaps the plane's icon for its
model, so a pick at click time found a different plane behind it.
- For flights, military, satellites and live vessels, whose own click
already follows the craft, Context no longer starts a second follow: the
flights layer read that as a click on empty map and let go. The card is
marked as following once the camera has taken hold.
- The card's following state resets when the camera stops following, so
picking the same item again follows it again.
- A click on open ground, sea, sky or the photorealistic ground clears the
card.
Clicking anything a layer can identify opens one card in Context: a hero
tile (route globe and 3D model for a flight, the camera for CCTV, headline
figures otherwise), its facts, actions with Cockpit or the orbital view as
the primary one, and a standard set of nearby blocks (weather and local
time, flights, vessels, hazards, alerts) within one radius the user sets.
Aircraft show altitude as a graph. Things that move are followed when
picked, and a card closes when its layer is turned off.
With nothing selected the panel describes the view: the layers that are on
with a breakdown of what each holds, the camera's height, what is in view,
then time, weather and local news. From far out it shows worldwide counts
per layer. A search field in the header narrows whatever the panel shows.
Prototype. Context reads weather and hazard feeds while its panel is closed,
the two 3D previews on a flight card repaint continuously, Follow can show
pressed after tracking has ended elsewhere, and most new strings are fixed
English. Same-named sites are told apart by position, not by a stable id.
A resumed hold waited only its rest unless the layer gave a media gate,
and only trimmed clips have one, so an untrimmed clip started again (as
on Gyirong) was cut short. The layer now says when a run going on from a
seek started its clip again, and the hold then plays out as from its
start: through the media gate when there is one, else for the whole hold.
For a shot whose path runs during the camera move, a seek in the hold
showed its evidence sequence at the start and a resumed run jumped to
its end. The sequence now stands where its own clock has it (after the
clip and its exit), and a resumed run carries on from there.
The corner controls are the ACTIVE STYLE readout and any element marked
with data-stories-corner, looked for again for 20 s after Stories mounts,
in place of an element id this app never has.
The director's own pointerdown listener, added first, stops a run whose
camera it drives before Stories heard the press, so the tap still played
the story again. Stories now reads the press in the capture phase, and
its tap listeners are removed on teardown.
Three fixes to how the globe draws and reports loading.
**The idle frame rate is the app's rule.** The Cesium frame port capped the loop at `IDLE_FRAME_RATE` whenever nothing held it, so the rule lived inside the renderer. The render governor now sets the rate: the display's own while the loop is held, `IDLE_FRAME_RATE` while not. The frame port gains `onHeldChange(cb)`, which says when its first hold is taken and its last released (animated visual styles included), so the governor hears every hold. The quality setting's frame-rate cap is kept apart from the governor's rate, and the loop draws at the lower of the two, so neither overwrites the other.
**Line batching is timed.** A line set waited 30 drawn frames before its unchanged lines settled into a static batch (300 for the long wait), so the batch built twice as fast at 120 Hz as at 60 Hz, and took seconds at the idle rate. It now waits `SETTLE_MS` (500 ms) and `LONG_SETTLE_MS` (5 s), and moved shapes go back into their batches on the same timing.
**KEY REQUIRED.** A layer that cannot load without a provider key ended the global status chip LOAD FAILED. The chip now has a KEY REQUIRED outcome, ranked below a real failure: a layer whose stats say `keyRequired` ends KEY REQUIRED, any other failure still ends LOAD FAILED. Vessels report a missing AISStream key as `keyRequired` and name the key in the panel; a later outage clears it, as it is no longer the key that is missing.
Checked: the full suite (new tests for `onHeldChange`, the quality cap against the governor's rate, timed settling, and the chip with and without a key), format, boundaries, build, the stub renderer boot and the Cesium conformance run; in the browser, the idle and held frame rates; and the first-run check now asserts that with no keys set the chip never says LOAD FAILED.
Early Stories builds wrote stories, storyThumb and storyTags in version 6
projects, so those projects load again; the fields stay refused before
version 6. The version 6 round trip is tested again.
A camera move the scene drives frame by frame (an authored move, or a
flight resumed partway) stops the run on pointerdown, so the story read
as stopped when the tap ended and the tap played it again. The tap now
goes by whether the story was playing when it began.
Back or Forward into such an entry from Explore or an open story clears
the story and its time from the address and the entry's history state,
keeping the globe hash and, when the entry is Explore, Explore itself.
After placing the layers at the seek's moment, the hold settles them
without the seek, so the reveal continues from where the seek put it and
a clip the moment falls in starts again from its beginning (a clip
cannot be joined partway); one the moment is past stays finished.
The selected vessel's track drew every fix it held. Following the world
clock, it ran ahead of the icon to the vessel's newest fix; live, it
stopped at the last fix while the icon moved on from it. A change of time
restarted it from a single point until the track at the new time arrived,
so it went blank at every step.
- The track draws the fixes at or before the time the vessel is drawn at;
live, every fix.
- Each frame a head joins its last drawn fix to the icon where it is drawn,
as flight tracks do; none past TRAIL_HEAD_MAX_M (20 km), where the clock
has moved beyond the fixes the track holds.
- A change of time keeps the track, drawn up to the new time, until the
track at that time replaces it.
GEV stories never explore, carry no world time and are never live:
drop the resume play state, Jump to live, the exploring branches and
world-time arguments, the overridden play button rules, and the hidden
rail and fill. The legend reads a plain field instead of a mock one.