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]>
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]>
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]>
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]>
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]>
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 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]>
- One spacing, pause and cache for the whole tab, so a search box put up
again does not start afresh.
- A failed request or a timeout pauses suggestions for a minute, as a
refusal does.
- A number named as a card, a phone or an account keeps its digits
together, so no address is read out of them; a UK postcode written
without its space is a place, not a password.
- The docs say exactly what is sent.
Co-authored-by: Manjunath Paparaju <[email protected]>
An application may draw with a renderer's engine directly beside the
contract. ApplicationHooks gains engine, whose kind names the engine;
Cesium's plugin hands {kind: 'cesium', viewer}. An application draws only
with engines whose kind it knows, and what it draws is its own to add,
update and remove.
The speed control's first entry runs the world clock at real time, which 1× did not say beside 1 min/s, 1 h/s, 1 d/s and 1 wk/s. It now reads Real-time, translated in every catalog.
Clicking anywhere on a shot row (its number, title or summary line), or
pressing Enter or Space on its title, now selects the shot and loads it,
which is what the row's LOAD button did; the LOAD button is gone. In its
place, up and down arrows swap the shot with its neighbour through
SceneDirector.moveShot, which saves the project and publishes shot-moved.
The arrows are disabled at the ends and while the scene plays, and neither
they nor DEL load the shot.
Above the height stations draw at, the layer only said "Fly below 48 km to
a covered city" without showing which cities those are. Every system in
the registry now has a marker there: a green, white-ringed dot over its
city, 5 km up so terrain never hides it, shown only while the layer is on
and stations are not drawn.
Clicking a marker flies straight down into its city from 20 km, as an
explicit camera action through the shell's runNavigation, like News and
the weather layers. The markers belong to the layer for picking.
The logo in the title was only a picture. It is now a button, "Back to
live at the starting view": the world clock goes live and the camera flies
to the view the app started from, letting go of whatever it follows as
Reset Globe does.
The shell's returnToStart() does it. It flies to the `homeView` option of
createApplicationControls, which is the start view unless given: an
application that passes `startView` only to carry a view across a rebuild
can keep the logo on its own first view. START_VIEW is exported from
./application/controls for that.
The title heading keeps "GOD'S EYE VIEW" as its name beside the button.
A landing is judged by its height above the ground, which the drawn
height alone does not give at a high airport. Records keep the ground
the warm cache already reads (the surface a grounded contact stands on,
the floor under a low contact near the view or tracked) as groundM, in
the render height's reference, and observeLiveAircraft passes it on; NaN
where the layer does not know it.
A feed's ZVEH type held for any contact, so a test transponder at 77 m/s
drew as a car driving at airliner speed and a drone at 762 m as a car in
the air; a GRND station reporting 11,880 m drew as a mast in the sky.
ZVEH now holds only for a contact reported on the ground (or with no
altitude) at up to 40 m/s; anything else is classed as an aircraft. A
GRND station stands on the ground whatever height it reports.
A tracked aircraft's icon and 3D model keep the colours they have
untracked in Flights and Military Flights (no cyan, no lighter amber);
only the icon's alpha changes (stale fade, clear while its model draws).
A selected vessel or aid keeps its type colour instead of white, and a
tracked satellite's dot keeps its class colour instead of yellow. An
emergency stays red while tracked.
A civil aircraft was drawn as an airliner until its type lookup answered,
even when its feed already named the type: a helicopter showed the
airliner icon and model for as long as the lookup took.
- Flights classes every contact, and picks its model, by the feed's own
ICAO type designator from the first fix. A looked-up type replaces it
once the lookup answers and outranks the feed's on every later poll;
the lookup still runs and fills the type name and registration.
- A surface emitter category still keeps only a ground type (ZVEH, GRND)
from the feed.
- State vectors have no type field, so an /api/flights answer may send
`typeByIcao` beside them, by ICAO address, as `emergencyByIcao` is sent.
The regional adsb.lol fallback now sends it from each row's `t`.
When an application places live contacts itself, the tracked trail was cut at the layer's own delayed clock, which can run minutes behind the placed aircraft: the trail ended far behind the aircraft, and its head was dropped while that clock warmed up. The trail now reads the aircraft's time off its own reports at the point where it is drawn, for Flights and Military Flights.
Aircraft models multiplied their tint into the shaded paint (HIGHLIGHT).
A saturated tint zeroes every channel it lacks: the tracked cyan (no red)
drew a red helicopter solid black, day or night, and a white Cessna one
flat cyan. Tinted models now mix the colour in at 30%
(AIRCRAFT_MODEL_TINT_MIX), so the paint stays readable and the colour
still marks them; untinted models still draw their own colours, and the
IR boost stays flat white.
Neither the multi-part models nor the part shader were involved: old and
new GLBs, with and without the shader, render the same pixels, and an
untinted model at night is lit by the default ambient term.
The new conformance check draw.models.paint draws a model painted with
COLOR_0 under a fixed sun and reads its colour by day, at night, and
under a tint mixed in. The parts test model can now carry vertex paint.
A host-supplied placement's speed is how fast the marker is drawn. While it
waits for its fixes to catch up it stands still at 0, so tracked-aircraft
panels and the cockpit readout showed 0 m/s for an aircraft in flight.
displayedKinematics now takes derivedFromPlacement: when the drawn speed is a
placement's, the reported ground speed is shown, and the placement's only when
nothing is reported. The placement speed still drives motion and dead
reckoning. Civil and military tracked descriptors pass it from the new
_drSpeedPlaced scratch, which placeLiveAircraft sets.
Turning vessels on returned what the first live poll answered, so a
failing feed (such as a missing AIS key) made enable() resolve false and
the layer reported it could not be turned on. loadLivePositions again
resolves with nothing once the poll is done; going back to live reads the
poll's answer through its own path.
Aircraft icons are one size; helicopters turn a three-frame rotor while
airborne or moving; ADS-B ground vehicles share one amber sprite and
stations/obstacles one mast; vessels get hull sprites by type and one buoy.
Going live keeps contacts until the first live answer and replaces them by
id; fast playback holds before the loaded positions end and prefetches
ahead. Cesium models move their parts from the optional model part state.
The tracked-model checks zoom the follow camera to within 2 km of the plane,
and the grounded-model check parks the camera 2 km above the planes instead
of 8 km, since models now draw only within 3 km.
A selected plane is drawn by its own model, and its fleet model was let go once
that model drew. Deselecting showed the icon at once, and the icon stayed for
about a second while a new fleet model loaded.
The fleet model now stays loaded but hidden while the plane is selected, kept
where the plane is. Deselecting hands the plane back to it in the same frame,
and the icon shows only when there is no loaded fleet model. Military aircraft
share this code. Vessels never swap models on selection, so they had no flash.
An aircraft, vessel, transit or rail vehicle now draws as its 3D model only
when it is within 3 km of the camera, and as its icon farther away. A model
already drawn is kept out to 3.6 km, so a vehicle on the edge does not flicker.
Proximity and All use the same distance and still differ by how many models
they allow (150 and 350). Models are drawn at their true size: the minimum
pixel size that inflated distant models is gone.
The camera altitude above which no model is considered is now the highest
aircraft the layers draw (30 km) plus the 3.6 km, so a camera high above the
ground still models an aircraft close to it. Cockpit's aircraft silhouettes
keep their own 150/185 km and 400/450 km bands, since they are icons.
Both layers registered their time coverage with the page's world clock when
created and never unregistered it, so an application destroyed and started
again kept each old layer, and its scene and tiles, reachable through the clock.
They now unregister on destroy and register again on init, as earthquakes do.
Cesium switches the map stacks through its globe port, as any renderer
does, rather than through a map engine of its own. Every route keeps its
behaviour:
- Google 3D turned off is kept hidden, and shown again without loading it
anew; the key route's tiles take clamped marks, as the token routes' do.
- Esri goes to its deepest level (23); its "Map data not yet available"
picture is a missing tile, so the parent's imagery stays.
- Cesium ion's world imagery is Bing over HTTPS on any page, with ion's
credits; a token ion refuses refuses the switch, as before.
- Keyless terrain that does not answer is the flat ellipsoid, tried again
behind it; world terrain asks ion first, as before.
- window.__godsEyeView.tileset is the Cesium photoreal tileset.
createApplicationTools took the Stories page as the open_stories action
even when the app's voice options gave its own. voice.openStories now
takes precedence, spoken or typed, with the Stories page as the default.
- A route globe that cannot draw tells the card, which shows another view.
- A card opened before the model set has loaded waits for that load.
- The model turns at the same rate on any display, and holds still under
reduced motion.
- A hidden cockpit view stops drawing.
- The route plane keeps the craft's latest position through the fly-in.
- Metric altitude graphs keep main's 0.5% change threshold.
Co-authored-by: Manjunath Paparaju <[email protected]>