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.
A timed source of kind 'decoded' (capability imageryDecoded) names the slot a
time shows (slotAt), the slots to hold ahead (prefetch) and answers each tile
of a slot with an image, missing or defer. The Cesium renderer draws each held
slot as an imagery layer of its own, as it draws frames; the stub shows the
slot. The check globe.imagery.decoded covers it.
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 second click of a double click on NEXT was dropped, so the button
looked dead; it now moves to the next step, and only the launch itself
still takes a single click. Tab from the search bar or another control
jumped back into the card; the card no longer claims focus from the page,
and still takes it when focus has nowhere else to be.
Co-authored-by: Manjunath Paparaju <[email protected]>
The welcome hides the card while it is up and while BROWSE STORIES loads,
so the right column started level with the left one; when the welcome
closed, the card showed over the column until something else moved the
panels. The column is laid out again when the welcome is removed or its
loading class comes off.
Co-authored-by: Manjunath Paparaju <[email protected]>
From review:
- A press begun while the steps were changing and released after (a click
aimed at NEXT) ran ENTER GOD MODE; a press now belongs to the step it
began on. Keyboard activation is unchanged.
- BROWSE STORIES closed the card before asking Stories to open, so a
refusal (another mode holding the globe) left nothing on screen; the card
closes only once Stories opens.
- On phones a mission's error line was squeezed beside the checkbox and
BACK; it takes its own row above the buttons.
- CURRENT-STATE calls the YouTube, X, Instagram, LinkedIn and bilawal.ai
links the author's channels, as the card does.
Co-authored-by: Manjunath Paparaju <[email protected]>
Replace the single dense welcome card with three short steps: an
introduction to the modes, where to start (Space Missions, Environmental
or Explore manually, Explore selected by default), then quick tips (the
place tip points at the search bar) and links. Next and Back keep the
selection, and only Enter God mode runs a mission; double clicks, Enter
repeats and clicks during a step change cannot launch one. Skip and ESC
close the card for the session, as before.
Drop the Live Contacts tile and the old voice tip. Space Missions
switches on its layer, which opens its own panel, so no first-run choice
enters a Context mode or opens the Context panel any more, and that path
is gone. The last step links to the repository and
Halfpixel's channels, each opening in a new tab without opener or
referrer. Its GEV Stories card closes the welcome and opens the in-app
Stories Explore view; the Stories announcement stays hidden, and unseen,
until the card has closed and Stories has loaded. The dim layer behind
the card is a click-through tint with no blur.
Update the 13 catalogs, CURRENT-STATE, the first-run QA harness and its
mutations, and the scripts that dismissed the old card. Add a changelog
fragment.
Co-authored-by: Sameh Khamis <[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]>
The card fades in from transparent, and the right column skips
transparent obstacles, so the layout run when the card arrived missed it
and the column stayed under it until something else moved the panels. The
end of the fade now lays the column out again; it also replays when the
card is shown again after the loading screen, recording or clean view.
Co-authored-by: Manjunath Paparaju <[email protected]>
From review, checked in headless Chromium at 1100-1920px wide, Tactical
and Minimal, left to right and right to left, with a credit line long
enough to wrap:
- Right to left with the Minimal HUD the credits stayed bottom left,
under the language picker and Power Up: the Minimal placement's two IDs
outweighed the right-to-left rule, which now matches it.
- Right to left from 1200px a wrapped credit line ran into the Tactical
bottom-right readout (AIS); the readout sits 1.5rem higher there.
- The left rail no longer reads a top pin no stylesheet sets since Cyber
went; VUE-MIGRATION no longer lists the removed cyberTheme test, and
CURRENT-STATE notes the narrow-screen credit line that does not wrap
(as on main).
Co-authored-by: Manjunath Paparaju <[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]>
With the Omnibar's lifted dock the right column rises level with the left
one, under the NEW GEV Stories card, whose buttons then took clicks meant
for the panel's controls (Street Level's FIT and FILL). The card is now an
obstacle for the right column, and its arrival or departure lays the
column out again.
Co-authored-by: Manjunath Paparaju <[email protected]>
From review:
- An error goes when a chip is chosen, and a search's error shows only
under the line it was for: a lookup that fails after the line was edited
says nothing under the new text.
- With voice on the field is hidden: "/" and Cmd/Ctrl+K no longer focus
it, and nothing is looked up for it.
- Without the action runner a refused or cancelled search keeps the line,
as the plan path does (only true is success).
- Text an input method is still composing is read when it is committed.
- A held or repeated Enter does not restart the same line over its flight.
- A city chip for the city whose landmarks are open flies there instead
of folding the landmarks.
- "villages around here" is looked up again for the current view.
- Data Layers takes the full lane only where the desktop dock is laid out,
by the condition omnibar-dock.css uses.
- On short phones the HUD readout moves under the field it shared a row
with.
- CURRENT-STATE says the phone gains a field and which places are kept.
Co-authored-by: Manjunath Paparaju <[email protected]>
A place row sent its name with its coordinates, and a name that matches a
city preset wins over them: "Paris, Texas" flew to Paris, France. Only the
coordinates go now. The bar's styles and dock tests join the format scope
and the bar its package.
Co-authored-by: Manjunath Paparaju <[email protected]>
On desktop the dock becomes one search bar (Omnibar.vue) that shows the
rows the line-reading pipeline makes: places with nearby suggestions,
coordinates, map items, layers, commands, plans such as "go to Austin and
show flights", guided walks through the real controls, and Ask GEV for
questions. Enter runs only what the line asks for outright. The map
credits move below the bar onto the Power Up row, the voice waveform
shows in the bar while voice is on, and the dock's Location and Visual
trays are hidden in this layout. The phone layout is unchanged. Long
place names are kept out of automatic Ask GEV.
Co-authored-by: Sameh Khamis <[email protected]>
From review of the first pass:
- Places again: "Secret Key Lake", "Access Token Road", "GATE CODE LANE",
"OTP Bank", "Auth Code ABCD Street", "California 90210-1234",
"Cambridge MA. 02139-4307", "12, 10115 Berlin". A key after a space must
be long, a bare code must hold a digit or be capitals after a label
that is not and end the line, and ZIP+4 follows a state's code or name.
- Private now: "gate code: abcd", "PIN A7B2", "OTP-ABCDEF", "login code
ab-12-cd", "auth_token=abc".
- The same text asked while its request is out waits for that answer,
however slow it is.
- A street without a house number is not named by the street alone.
Co-authored-by: Manjunath Paparaju <[email protected]>
- Not sent any more: "john @Gmail.com" (a capital after "@"), "030 12345"
and "Alice 12345-6789" (read as a house number and postcode),
"access_token=abcdef", a key in quotes or brackets, and letter codes
after a code label ("OTP: ABCDEF", "verification code ABCDEF").
- Sent now: "10 Downing Street SW1A2AA, London" (the comma hid the
postcode). "Pin Oak" and "Gate Code Lane" stay places.
- A house Photon returns without a name is named by its number and street,
so 10 and 12 Downing Street are two suggestions, not one "London".
- The same text asked twice at once is sent once.
- The village pack's build finds twins near the poles and across 180°;
the shipped tiles are unchanged.
Co-authored-by: Manjunath Paparaju <[email protected]>
- "hide flights near Left Bank, Paris" closed the left panel: a side is
closed only when the clause names nothing but the side.
- "flights near Trinidad and Tobago" looked up Trinidad alone, and "take me
to New York City NY" nothing (the command's words counted against the
name): the whole place is looked up, and the limit counts its words.
- "flights near 30.27, +97.74" and "30.27; -97.74" were split at the sign or
semicolon; both stay coordinates.
- "hide flights, show ships" listed "No layers are on": several requests in
a line are read as one plan, as with "and".
Co-authored-by: Manjunath Paparaju <[email protected]>
- "go to 30.27, -97.74", "go to 14R PU 2090 4906" and "flights near
30.27, -97.74" were refused as private (their digits) or sent to the
place service as text; coordinates named as the line's place are now a
spot to fly to, and the rest of the line is what the privacy rules read.
- A count ("flights over Texas") is offered only for a layer in or near
a place: "Ship Bottom", "Radio City Music Hall" and "radio settings"
are no longer counts that Enter would run.
- "go to ," sends nothing to the place service.
Co-authored-by: Manjunath Paparaju <[email protected]>
A pure pipeline the search box will show its rows from: omnibarIntent.js
parses a line (a place, a layer, a verb, a question, a panel's text),
omnibarEnter.js picks what Enter does, omnibarGuide.js answers "how do
I" for each feature, and omnibarRows.js turns all of it into rows. Its
strings are translated into every shipped language.
Co-authored-by: Sameh Khamis <[email protected]>
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 tile that cannot be read is left out of placesNear's answer instead of
failing it; without the pack's index the cities are still the answer.
- The build no longer inlines the small tiles into one chunk that loaded
with the first lookup: all 732 are their own files.
- A row at latitude 90 or longitude 180 is tiled where the lookups read it.
- --min-population 0 is taken as 0, not as the default.
Co-authored-by: Manjunath Paparaju <[email protected]>
137,662 places of 1,000 to 14,999 people that Wikidata gives a population
and coordinates for, none already in the cities pack, in 732 tiles of
5 x 5 degrees with an index of row counts (CC0). Nothing loads with the
app: a lookup reads the index once and then only the tiles it touches.
placesNear lists the places around a point, and findPlace finds a small
place by name near the view when no city of that name is near. The cities
build script writes the tiles with --tiles; the step from rows to files is
checked offline.
Co-authored-by: Sameh Khamis <[email protected]>
- The first height that replaces the entry frame's now moves only the
anchor's height. The anchor keeps its place and its eased lift, so the
camera no longer jumps to a corrected fix or steps back.
- A detail line is measured with the title's glyph widths. They are a
little wide for its smaller type, so a long detail line is no longer
clipped.
- The first aircraft update is checked in the existing test, and the copy
is removed; test fixtures are simpler.
- Comments, the release note and CURRENT-STATE match the code.