Merge branch 'main' into fix/b-awareness-marker-km

This commit is contained in:
Sameh Khamis committed 2026-11-01 22:40:10 -08:00
commit 2124f56f92
40 files changed
+546 -48

No files matched your search

+3
View File
@@ -0,0 +1,3 @@
- Show a vessel course of 359.5° or more as 0°. Vessel cards and the AIS HUD
rounded the course without wrapping, so a ship with no reported heading on
a 359.7° course read "360°" and "HDG: 360DEG" (Aditya, @Rohilalala, #1432).
+3
View File
@@ -0,0 +1,3 @@
- Show a CCTV camera facing 359.5° or more as HDG 0°. The HUD heading token
and the camera panel rounded the bearing without wrapping, so a camera
facing 359.6° read "HDG 360°" (Aditya, @Rohilalala, #1441).
@@ -0,0 +1,3 @@
- Label a route, arrow or drawn line of 995 m or more as 1.0 km, and of
9,950 m or more as 10 km. The placed label picked the unit before rounding,
so it read "1000 m" and "10.0 km" (Aditya, @Rohilalala, #1445).
+3
View File
@@ -0,0 +1,3 @@
- Show a route of 9.95 km or more as 10 km. The Directions row and step
cards kept one decimal until the raw distance reached 10 km, so 9.96 km
read "10.0 km" (Aditya, @Rohilalala, #1450).
+2
View File
@@ -0,0 +1,2 @@
- Show an ALPR camera's mapped bearing of 359.5° or more as DIRECTION 0°
rather than DIRECTION 360° (Aditya, @Rohilalala, #1451).
@@ -0,0 +1,5 @@
- Describe a selected flight or military contact on 359.5° or more to the
voice assistant as heading 0°, not 360° (Aditya, @Rohilalala, #1454).
- Heading and bearing readouts share one rounding helper, so the Cockpit's
TRACK ACQUIRED course no longer reads 360°, and a negative bearing wraps
instead of printing a minus sign (#1454).
+4
View File
@@ -0,0 +1,4 @@
- `build/register-vue` loads components on the test thread and keeps compiled
components between test processes in a per-user cache directory, so Node
tests that import views run about twice as fast. `GEV_VUE_CACHE=0` compiles
every time (samehkhamis, #1500).