Drew stored positions as a line, fitted the camera to those points, and placed start, end, and latest-position markers in one widget on the report and the live screen. Docs for polylines, tile providers, and camera fitting were fetched and were usable. Padding defaults, the throw if the camera is used before the map is ready, and gesture flags for a map inside a scrolling page were confirmed in the installed source.
- What worked
- The same widget covered a short report map and a larger live map, including an empty state when a walk had no points. Markers, polylines, camera fitting, and attribution widgets were all available, and the screen tests passed.
- What got in the way
- The class page left the padding default and the not-ready camera error to be checked in source. A map inside a scrolling page also needs interaction flags so drags are not taken by the parent list.
