Grayed-out duplicate routes. The on-board "Fly to …" button and the Relocate GO are now disabled (with a hint) when the click would hit the server's 409 "{ICAO} is already in the flight queue"; already-active/queued airports also render as disabled options in the relocate select. Server-side guards untouched.
Hover trace from the landing airport. Hovering an on-board parcel while its carrier is mid-flight now draws the dotted trace from the leg's landing airport, not the plane's live position (grounded carriers keep today's behavior). A package destined at the active leg's destination draws no extra line — the solid active leg already covers it.
Entire queue as dotted lines.queuedRoutesGeoJson now also draws grounded planes' pre-built queues (location → queue[0] → …); flying planes are unchanged. New unit pins for the grounded chain, unknown-first-point skip and repairing no-draw; e2e gains a grounded-queue map test and the mid-flight hover spec was reworked to pin the landing-airport start.
Fixes #77
All three sub-items of the queue UI issue:
**Grayed-out duplicate routes.** The on-board "Fly to …" button and the Relocate GO are now disabled (with a hint) when the click would hit the server's 409 "{ICAO} is already in the flight queue"; already-active/queued airports also render as disabled options in the relocate select. Server-side guards untouched.
**Hover trace from the landing airport.** Hovering an on-board parcel while its carrier is mid-flight now draws the dotted trace from the leg's **landing airport**, not the plane's live position (grounded carriers keep today's behavior). A package destined at the active leg's destination draws no extra line — the solid active leg already covers it.
**Entire queue as dotted lines.** `queuedRoutesGeoJson` now also draws grounded planes' pre-built queues (location → queue[0] → …); flying planes are unchanged. New unit pins for the grounded chain, unknown-first-point skip and repairing no-draw; e2e gains a grounded-queue map test and the mid-flight hover spec was reworked to pin the landing-airport start.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Fixes #77
All three sub-items of the queue UI issue:
Grayed-out duplicate routes. The on-board "Fly to …" button and the Relocate GO are now disabled (with a hint) when the click would hit the server's 409 "{ICAO} is already in the flight queue"; already-active/queued airports also render as disabled options in the relocate select. Server-side guards untouched.
Hover trace from the landing airport. Hovering an on-board parcel while its carrier is mid-flight now draws the dotted trace from the leg's landing airport, not the plane's live position (grounded carriers keep today's behavior). A package destined at the active leg's destination draws no extra line — the solid active leg already covers it.
Entire queue as dotted lines.
queuedRoutesGeoJsonnow also draws grounded planes' pre-built queues (location → queue[0] → …); flying planes are unchanged. New unit pins for the grounded chain, unknown-first-point skip and repairing no-draw; e2e gains a grounded-queue map test and the mid-flight hover spec was reworked to pin the landing-airport start.