2 Commits

Include renames

Author	SHA1	Message	Date
Constantin LeueandClaude Sonnet 5	3091476771	Fix wheel/panel layering, add bottom-bar background, and full-screen charts ... - Wheels/readouts now add max(MediaQuery.padding.left/right) on both sides symmetrically (HTML prototype: max(env(safe-area-inset-left), env(safe-area-inset-right))), so a front-camera cutout in landscape doesn't sit behind the altitude wheel, and both sides stay in sync. - WaypointListPanel is now pushed via Navigator (PageRouteBuilder + fade) instead of being an internal Stack overlay in PlanScreen. It was rendering *under* AppShell's TopModeBar before, since TopModeBar is always the last (topmost) child of AppShell's own Stack regardless of what PlanScreen draws internally - a plain bool flag inside PlanScreen had no way to paint above a sibling higher up the tree. A pushed route paints above the entire invoking route's content by construction, so this was the actual fix rather than reshuffling Z-order inside PlanScreen. - Extracted DefaultDroneProfile (T1 Ranger constants) out of PlanScreen's private statics into lib/domain/mission/, since WaypointListPanel now needs the same values to compute its own route geometry reactively (previously passed down as a vertexBad/altMin/altMax/... snapshot, which would have gone stale while the panel was open across a route boundary). - Bottom bar now has the prototype's rgba(15,15,15,0.72) background (previously fully transparent outside the stats pill), and gained MiniAltitudeProfile - the non-interactive height-profile sparkline that sits above the stats row. - Added the Altitude/Speed full-screen chart tabs (FullValueChart): drag any waypoint's point to adjust its altitude/speed, X position proportional to cumulative route distance, matching the prototype's buildFullChart()/attachChartDrag(). Terrain overlay and wind diamonds from the prototype aren't ported - terrain (doc 3.9) and wind (doc 3.8) systems don't exist yet in the Flutter app. - RouteGeometry now also exposes legClimbBad (was computed internally but not surfaced), needed by both the mini profile and the chart tabs. Discovered while updating the widget tests: a single tester.pump() after tapping something that triggers Navigator.push/pop isn't enough - the push/pop itself needs a frame to register before a duration-based pump can animate it, so both are needed in sequence. Added 2 new tests for the chart tabs; all 17 tests and flutter analyze pass. Verified all four changes on the Pixel_10a emulator: wheels, opaque bottom bar with the mini profile, the list panel now fully covering the top bar (confirmed by its complete absence while the panel is open), and dragging points on both chart tabs. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-07-28 08:13:01 +02:00
Constantin LeueandClaude Sonnet 5	d3c5a68636	Add waypoint list panel and bottom stats bar ... - BottomStatsBar: persistent "Details: N WP · dist m · duration" pill (HTML prototype's #bottomBar/#statsRow), tap opens the full waypoint list. Mission/drone name and the Send button are intentionally not part of this - mission library and upload aren't wired up yet. - A warn banner ("Route exceeds drone capabilities at highlighted point") appears above it whenever buildRouteGeometry finds a bad vertex or leg - a direct, low-effort payoff from the fillet geometry work. - WaypointListPanel: full-screen overlay listing every waypoint (altitude/speed/execute/catch radius), matching the prototype's List tab. Only one row editable at a time; editing swaps plain text for draggable WaypointChip values and an execute dropdown. Row tap (outside edit mode) centers the map on that waypoint and closes the panel; delete removes it and adjusts the reticle's target index the same way the halo menu's remove already does. - WaypointChip: vertical-drag value chip (HTML prototype's .value-chip), fixed step of 10 per 14px matching chipFieldConfig - simpler than the original's dual vertical/horizontal axis-lock gesture, which felt like more fidelity than the interaction warrants here. - Provider gained setCatchRadius and setAction (direct assignment, as opposed to toggleAction's toggle-to-none semantics used by the halo menu) to support the list's editable fields. - Altitude/Speed full-chart tabs from the prototype (drag-to-adjust altitude/speed profile charts) are a separate, larger feature and not part of this step. Centering on a waypoint from the list calls MapController.move(), which - like the reticle's auto-snap - doesn't emit MoveEnd, so snap detection is invoked manually afterward to match the prototype's resulting behavior. Added 4 widget tests (open empty list, row-tap centers and closes, delete removes and updates the empty state, chip drag updates altitude) - one required a pump(duration) after the drag to flush the chip's 120ms flash Timer, which was otherwise still pending at test teardown. All 15 tests and flutter analyze pass. Manually verified on the Pixel_10a emulator: opened the list with two waypoints, edited a row's altitude via chip drag (confirmed value change, accounting for device-pixel-ratio scaling vs the widget-test logical-pixel case), and confirmed row-tap re-centers/closes. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-07-28 07:25:32 +02:00