- The flight after a count click checks the frame on both axes and at the
height of the highest mount, so a group on a slope or in a very wide
window stays in view; when it cannot, it flies to the nearest cell with
two or more cameras, never to a lone camera that joined the count.
- A count takes a click over a background fill no layer owns (earthquake
discs, fire perimeters), and still yields to a scene item another layer
registered.
- A count crossing the HUD edge refreshes the view only when the active
icon or a lone camera depends on it, and never mid-motion, so panning no
longer runs extra full view passes.
- A count restored at the HUD edge keeps the lone cameras its outline
covers, and leaves the others as icons.
Fixes from review of the move to StreetLevelPhotoViewer:
- Each mount and each panorama canvas now takes a key no viewer reuses,
and the view keys its root by the mount. Before, switching KartaView and
Panoramax in one tick let Vue patch the old viewer's canvas, whose
destroyed renderer had lost its context, into the new one, so 360°
photos fell back to their front view.
- Of the viewers mounting in the host, the view draws the one mounted
last, by mount key (photoViewers.js, which subscribePhotoViewer() now
uses), whatever order they present in. A viewer still mounting when a
later one is drawn is superseded: it unmounts and its mount fails as
closed, rather than staying pending and being drawn once the later one
goes.
- A panorama's first image is uploaded once the view has drawn its canvas
shown (the view hands the canvas back on every draw), so it is never
sized into a hidden canvas.
- The tests' fake view now draws as Vue does: once per tick with the final
value, keeping elements while their keys are unchanged and handing every
element back on each draw. StreetLevelPhotoViewer.test.mjs covers the
switch in one tick and the overtaken mount with the real view.
- The guard test's check that the photo viewer writes no DOM covers
inserting, moving, removing and replacing elements, attributes, classes,
styles and the hidden, disabled and text properties.
Co-authored-by: Manjunath Paparaju <[email protected]>
The photo viewer KartaView and Panoramax share (photoViewer.js) no longer
builds its root, picture, panorama canvas and ‹ › buttons in script. It
presents them through subscribeView(), which the street-level layer
gathers in subscribePhotoViewer(); the application shell publishes that
to the gev-street-level-photo store, and StreetLevelPhotoViewer, beside
the Street Level panel in the layer panels, teleports the viewer into the
viewer host with the same classes, data attributes, labels and order. Its
‹ and › are ghost UiButtons. The view forwards keys, pointers, wheel, the
step clicks and a lost WebGL context to the viewer and hands each element
back: the canvas the panorama is drawn on (a fresh, keyed one after a lost
context, which an open now waits for), and the frame, picture, root and
buttons the viewer measures and keeps focus with. The viewer keeps every
decision: loading, upgrades, size limits, keys, drag, pinch, zoom, Esc on
the viewer's box and focus when a step button disables. The street-level
layer still needs no Vue; with no view subscribed these photos cannot
mount, which docs/VUE-MIGRATION.md records.
The provider and viewer tests draw the viewer with a fake view in
kartaViewFakes.mjs; StreetLevelPhotoViewer.test.mjs runs the real view on
a page, and streetLevelPhotoControls.test.mjs pins the kit controls. The
panel page's lost-graphics notice in globePanelRuntime.js stays built in
script, as the document now says.
Co-authored-by: Manjunath Paparaju <[email protected]>
- A count click stands aside when an overlay label or another layer's card
already took the click, and CCTV now claims a count click in the shared
pick registry, so the flights layer no longer reads it as an empty-map
click and keeps tracking its aircraft.
- The flight to a group halves the distance only while the group stays in
frame; otherwise it flies to the nearest ground cell of the group, so a
tilted click no longer ends with no camera on screen.
- Counts hidden under the HUD no longer push the active icon aside, and a
lone camera that would move a merged count under the HUD leaves the
original count and its icon as they were.
- Cameras on one mount are spread before counts merge, so a spread icon no
longer slides under a neighbouring count.
- The ground module comment says how a camera without a batch height takes
the drawn terrain.
The test's camera and rendering doubles now carry what focusing a mission
uses, so without the cockpit guard the test fails on the camera flight
rather than on a missing double.
Co-authored-by: Manjunath Paparaju <[email protected]>
Focusing a mission does nothing in the cockpit, so the layer row's arrows
select the next mission without moving the camera, as its label and dot
already do.
Co-authored-by: Manjunath Paparaju <[email protected]>
The cockpit holds the camera: the mission dot, like its label, selects the
mission there without flying to it, and a mission picked in the cockpit is
not flown to when the active satellite lookup returns.
Co-authored-by: Manjunath Paparaju <[email protected]>
Under the card-on-top rule a mission label is the card on top for the
cockpit too, so the label no longer steps aside there: it selects its
mission without moving the camera the cockpit holds. Tests and docs no
longer claim a covered click reaches what lies under the label, and the
busy-restore note says an explicit Satellites action lets the saved state
go.
Co-authored-by: Manjunath Paparaju <[email protected]>
Main's single click rule (the card or label on top takes the click, read
once per click through clickCard and isUnderOtherCard in
src/data/pickRegistry.js) covers a click on a Space Missions label: a
mission marker label is an interactive world-overlay entry, so the
host's hit test names it as the card on top for every other layer. The
per-layer label guards in CCTV, Drone Airspace, FIRMS, Ghost Maps, News,
Perimeters, Shipwrecks, Vessels, Wildlife Sightings, ALPR, Local ADS-B
and the cockpit orbital focus are dropped for main's versions.
The mission-label tests are kept on main's API: fakeInputUnderLabel now
also names the label as the card on top, and each test shows a click on
the label never acts on the card, camera, vessel, fire, reader, aircraft
or report under it, and leaves the selection as it is. A launches test
checks that a mission label is interactive and is the card on top for
every other layer. Docs, changelog and the dispatcher's `overlay` note
describe the merged behaviour.
Co-authored-by: Manjunath Paparaju <[email protected]>
Resolves conflicts with main: a world focus target's own range past its
framed radius replaces the kind's range (#1832), so a quake asks for its
own range only past M6 and the earthquake framing stays its floor; FIRMS
keeps main's marker stand-in under the card-on-top rule; launches keep
main's label click and also read the card on top through the pick
registry.
Review fixes for #1781:
- One rule for cards: the world-overlay host hands its hit test to the
pick registry, and every click handler reads the topmost interactive
card or label once per click (`clickCard`, `isUnderOtherCard` in
src/data/pickRegistry.js), so all handlers agree in any listener order.
A layer whose own card or label is on top acts on it whatever is drawn
under it; a layer under another layer's card neither acts nor treats
the click as empty space (a tracked aircraft stays tracked, a selection
stays selected); Context names nothing under a card. A selected news
card over a vessel no longer opens the link and selects the vessel.
- With one rule, the per-owner arbitration options are no longer read
and are removed: `passive`, `expanded` and `declinesClick` pick owners,
`rememberClickPickActions`, `isActedOnByOtherLayer`, card backgrounds
and `cardKeepsClick`. The dispatcher is unchanged from main.
- A drag that ends on a quake disc, label or card does nothing; opening
the USGS page or clearing the selection needs a clean click.
- A click on the map under another layer's card opens no Street Level
ground image.
- A CCTV card that is going away is still not the scene under it.
- Docs and changelog describe the new rule.
A place search or fly-to stops satellite tracking with the tool origin,
which the saved Satellites state did not take in, so a satellite tracked
by voice during the mission was tracked again when Space Missions ended.
The saved state now takes in every deliberate Satellites setting (person,
voice or tool), as the layer state does.
Co-authored-by: Manjunath Paparaju <[email protected]>
setMarkerStandIn takes an optional focusRangeM(record): when a click on a fire the stand-in draws moves the camera there, it stands off that many metres instead of the usual fire framing. A world focus request may carry its own rangeM; past the framed radius it replaces the kind's range.
A setting such as "show orbits" changed by the person or by voice while
Space Missions keeps the Satellites state from before it (while it runs, or
after a restore that found Satellites busy) was overwritten when the mission
ended. It is now kept in that saved state, as their visibility choice is.
Co-authored-by: Manjunath Paparaju <[email protected]>
A saved Satellites state kept by a busy restore could still carry the mark
of a Satellites switch the person made after it, which tells the restore to
leave Satellites as it is. Space Missions turned on again kept that mark,
so turning it off left Satellites on when it had been off. The next mission
now saves Satellites as it is when it starts in that case.
Co-authored-by: Manjunath Paparaju <[email protected]>
ALPR, News, Wildlife Sightings, Fire Perimeters, GhostMaps and Drone
Airspace each skip their own card or overlay hit test when a painted label
took the click. Each now has a test that a click the label took does not
select the camera or sighting, open the report, or open the card's link,
and lets go of the current selection, while the same click off the label
still acts. ALPR's presentation gets its first test file.
Co-authored-by: Manjunath Paparaju <[email protected]>
A restore that found Satellites still busy keeps the saved state, and the
next Space Missions start then skipped switching Satellites on, so it came
up with no satellites. It now keeps that saved state (still the one from
before the mission) and switches Satellites on for the mission again.
Co-authored-by: Manjunath Paparaju <[email protected]>
A click on a Space Missions label reaches every click subscriber so they can
let go of their selection, but the layers that test their own painted cards
or pick the scene themselves still found what lay under the label: CCTV
turned that camera on, FIRMS and Vessels selected and flew to theirs, News
and Wildlife Sightings opened their item, Perimeters, Ghost Maps and
Shipwrecks opened the card's link, ALPR selected its reader, and Local ADS-B
drilled the scene itself and selected the aircraft. Each now skips its own
test on such a click, and Local ADS-B drills through the click, so the click
only releases selections, as a click on empty map or another layer's
contact does. Ordinary clicks behave as before.
Co-authored-by: Manjunath Paparaju <[email protected]>
The fire layer takes a stand-in for its markers (setMarkerStandIn({ hitTest })): its glows, heatmap and ambient cards are hidden, and a click the stand-in answers selects and focuses the fire exactly as a marker click does.
While Space Missions was going off (its Satellites restore still running,
the panel still shown), hovering or keyboard-focusing a roster row still
scheduled the roster preview, which flew the camera to that launch with
nothing left to end it. The preview is no longer scheduled once the layer
is going off, and one already pending is dropped. Selection, focus, replay
and stepping from the Data Layers row were already refused then.
Co-authored-by: Manjunath Paparaju <[email protected]>
A click a painted overlay handled, such as a Space Missions label, returned
before any click subscriber ran, so the layers that close their cards or let
go of their selection on a click never heard it. Now only the picking the
label replaces is skipped: subscribers still hear the click, marked as an
overlay click whose hit is the label (no draw set, no id, nothing drilled),
and the geometry beneath it is not picked.
Co-authored-by: Manjunath Paparaju <[email protected]>
When Satellites had not settled within the 30 s limit, turning Space Missions
off cleared the saved Satellites state and put the parameters back before
failing, so Satellites stayed on as Space Missions had switched it with
nothing left to retry. Now a busy Satellites layer is left untouched and the
saved state is kept, so turning Space Missions off again finishes the
restore. A Satellites action the person took still gets its parameters back.
Co-authored-by: Manjunath Paparaju <[email protected]>
From review:
- Voice "open the Space Missions panel" under the Cockpit opened it and
wrote its preference; it is refused there now, as the layer's own reveal
is. On a phone the panel's Missions sheet shows too.
- A voice "context off" switches Space Missions off only when no Context
mode is on, entering or starting (Contacts), and it also reaches Space
Missions while the layer is still starting.
- While the layer is going off (its Satellites restore may still run) a
roster click, focus or replay does nothing.
- Stepping missions from the Data Layers row opens the panel, as a globe
pick does.
- SHARE-LINK-FORMAT lists panel 11, space-missions-panel (token n).
Co-authored-by: Manjunath Paparaju <[email protected]>
Space Missions no longer runs as a Context mode. The launches layer owns
its Satellites dependency, including the rule that a Satellites off
asked for after Space Missions was switched on ends it (request order
decides), and a small controller connects the layer to its own panel and
store. Context no longer isolates, snapshots or restores Space Missions
or Satellites, so Contacts and Space Missions run together in either
order, and scene playback no longer exits an isolating mode. Settled by
the owner: Contacts leaves Satellites as it is, and only a person's or
voice Satellites off ends Space Missions; a scene, story, preset or
other programmatic off does not.
Turning the layer on by hand or by voice, choosing it at first run, or
picking a mission on the globe opens the Space Missions panel, and on a
phone its Missions sheet. Asking voice to open the panel while the layer
is off is refused with a reason, and voice never opens it while the
Cockpit owns the screen. With no Context mode on, a voice Context off
switches Space Missions off. A failed Satellites restore no longer cuts
the layer's teardown short. Mission labels on the globe select their
mission. The layer names a failed first index load itself, so the
Context toast no longer imports Space Missions code.
Also carries the satellites request ordering and
DataLayerManager.waitForLayerIdle, the share token for the panel, voice
panel ids, Cockpit folding the panel away and the phone tab ellipsis.
The panel shares the rail gutters and hover border of the other side
panels.
On top of the Omnibar: "open space missions panel" reaches the new
panel, and Open Context no longer answers to "missions".
Co-authored-by: Sameh Khamis <[email protected]>
Display > HUD > Sonar now turns the sonar sweep on over Tactical or
Minimal. It is off by default, ON reveals its five sliders, and it keeps
its guards: an OFF control, the sweep only while the HUD is visible and
outside Cockpit, no animation under reduced motion, and repaint timers
re-armed only after a drawn frame that still shows contacts.
The Cyber layout, its shell skin and its Cockpit lanes are removed. Share
links, scenes, saved views and set_hud that name Cyber open Tactical with
Sonar on; links and scene shots record Tactical with Sonar under the same
code, and a restored state that names another layout turns Sonar off.
set_cyber_sonar keeps its name and works under any layout. A newer Sonar
toggle or voice setting wins over a share-link restore that lands later.
From 1200px wide the command dock and World Timeline sit 74px above the
bottom edge, as in the Omnibar layout, leaving the bottom row to the map
attribution (left) and the Power Up corner row (right). The attribution
moves to the bottom right when the page runs right to left, where the
corner row sits at the bottom left, and a long credit line wraps upward
before reaching the corner row. The Tactical bottom-right readout sits
8px above Power Up and the coordinates start level with it. The World
Timeline is narrowed to sit between the corners. Toasts keep clear of
the raised dock and the chat and voice panel height budgets subtract its
rise. Below 1200px the layout is unchanged. The left rail treats the
centered World Timeline and voice control as obstacles only where they
reach a laid-out panel.
On top of the Omnibar: sonar.css replaces cyber.css after the Omnibar
imports, the Omnibar's HUD guide step now says Layout picks Tactical or
Minimal, and the Omnibar's Tactical bottom-right readout keeps the same
8px above Power Up.
Co-authored-by: Sameh Khamis <[email protected]>
Bugs:
- Cameras on one mount stay side by side after their geometry is built,
so a click or a settled view no longer folds them back into one icon.
- A count click yields to a card drawn over the marker and to another
layer's object under it, waits while the cockpit or tracking holds the
view, and flies at most halfway, so a long chain of cameras still splits.
- The active camera's icon is never covered by a count, transparent
corners of the marker no longer catch clicks, and a count hidden under
the HUD keeps its lone cameras.
- A lone camera joins only its nearest count and never bridges two; cameras
close enough to draw as icons take part too, at their drawn icon size.
- Groups across the antimeridian keep their longitude; the flight frames
the highest mount; markers on ground below the ellipsoid stay visible;
counts fade outside the Scope circle.
- Mounts less than a metre apart count as one mount.
- A drawn-terrain height survives a late fallback answer, is read for an
unresolved camera and for one projected off the window, is re-read when
the terrain under it finishes loading or the terrain source changes, and
the read budget no longer goes to the same misses each pass.
Cleanup: the glyph draws from one green SVG sprite instead of recolouring
pixels, marker-only constants move next to their use, layout tests check
behaviour rather than formulas, and docs and comments match the code.
docs/I18N.md names the one fixed notation of count badges as an exception.
The fire layer module exports filterFires and DEFAULT_FIRE_FILTER, the filter its markers use, so an application drawing the same detections another way hides the same fires.
- A clock correction starts a new epoch, and playback may first draw its
second report. The turn point now resets on a new epoch as well as on a
break, so a standing train no longer turns around after a correction.
- recallDirection and earlierFixes are gone: comparing each earlier report
with the newest turned a standing train on GPS jitter. A train bound when
its line arrives late shows no direction until it has moved 15 m.
- Tests share reportDirections, iconOf and the playback helper.
- Comments and CURRENT-STATE match the code.
When the terrain height batch loses a chunk to the rate limit, the cameras
in it keep a sea-level fallback height. In the mountains that put them far
under the surface, so the view pass judged them by a point that was not
where they are drawn: a tilted view dropped the count marker, a click on
the marker framed empty ground, and icons drifted on tilt and pan.
- A camera with no real ground height takes the height of the terrain the
globe draws once it is near the screen (up to 300 reads a pass, through
the height service), and a later answer from the batch replaces it.
- A count marker is anchored to the drawn terrain under its centre, and a
click frames that ground.
- Cameras on one mount draw side by side, 30 px apart, each with its own
callout, instead of as one icon with several callouts.
The photoreal map stack is not covered: terrain is not the surface there.
A ground cell with one camera always drew its icon, so at some zooms a
camera poked out from under a count marker with its own callout.
An icon closer than the merge gap to a count marker now joins that marker:
the count grows by one and the icon, its callout and its card are not drawn.
Two lone cameras with no count beside them stay two icons, and the active
camera always keeps its own icon.
- GPS jitter under 15 m at a standing train no longer turns it, in reports
and in playback; a reversal needs at least 15 m of movement.
- A standing train keeps its operator's last bearing through reports that
leave it out.
- Playback resets its turn point at a break, so a jump to a corrected
position is not a reversal.
- A train bound while its line is still loading takes its direction from
the movement it already made.
- A vehicle in view that leaves a Transit hold goes on from its own clock
instead of rewinding.
- Tests cover the 15 m boundary, the late line, the hold release and the
icon after Transit is turned back on; duplicate jitter tests are merged.
- FOLLOW_MIN_MOVE_M is gone; comments and CURRENT-STATE match the code.
A count marker now says what it counts and how much:
- Its height grows with the count, from 40 px for two cameras to 58 px for
several thousand, with clear fill around the digits.
- A small single-camera map icon sits under the top of the ring and the
number just below the centre, so the two never touch. The icon is built
from the same sprite as a single camera on the map.
- Thousands print as 1.7K or 12K in every UI language.
- The camera layer is green: count markers and idle single cameras share
the colour, the active camera stays gold and live-video cameras violet.
A drifting touch tap or a cockpit-mode tap on a fire, quake or vessel card
beside an aircraft did nothing: the cards deferred to the aircraft, whose
click handler ignores such taps. Pick owners can now declare the clicks
they ignore (registerPickOwner(..., { declinesClick })); flights and
military decline a drag or a cockpit tap and CCTV declines any click that
is not clean, so a card over them keeps that tap.
Also from review:
- the selected quake's contour rings sit on the ground the disc is draped
on, re-read through the heights service while they paint;
- a label's fly-to frames the whole disc for large quakes;
- a quake that ages out of the feed clears its selection as evicted;
- id-less quakes are named by their content, not their row;
- the Bhote Koshi trigger-record callout opens its source on a click, as
its keyboard action does, and yields like the other cards;
- the card's place line is cut to 48 characters, its link hint shows only
with an opener, and its accessible name carries depth, place and time; a
link-less card's click and keyboard action fly to the quake;
- camera trace comparison scales its tolerance with the value and wraps
heading and roll.
The scene renders at CSS resolution and is stretched on a high-density
display, so a count marker drawn as a scene sprite looked coarse next
to the camera callouts, which the world overlay paints at device
density.
Paint the markers through the overlay's custom paint lane instead, in
the callouts' typeface. Each paint reprojects the group centres; a
click is resolved against the rectangles painted in the last frame and
still zooms to the group without choosing a camera. A marker that would
cover HUD chrome is skipped, as overlay entries are.
With no aggregate sprites left, the contact sweep no longer needs to
skip them, so that exclusion is removed.
- A train first seen standing takes its direction from the operator's
course, not from a course drawn out of GPS jitter.
- Moving a hold to another vehicle releases the first one the same way as
ending the hold.
- repaint always goes through placeSample, which hides the held vehicle and
puts it on its current segment, so setShown is no longer exported.
- Tests cover the icon right after a hold, a segment with one known floor,
a known floor at 0 m and selection by click after the layer comes back;
shared helpers replace repeated setup.
- Comments, CURRENT-STATE and the release note say what the code does
without internal figures.