Animate the radar timeline with a double-buffered overlay

Completes milestone 3: frames render over the map, play as a loop, and can be
scrubbed, with the legend drawn from the manifest rather than a constant that
could drift from what the worker actually rendered.

The overlay alternates two MapLibre image sources. Updating one source in place
flickers, because the layer briefly shows a half-written texture; adding every
frame as its own layer avoids that but pins them all in GPU memory, and twenty
512x512 RGBA frames is about 80 MB. Two buffers cost the same whether the
timeline holds six frames or sixty. Platform-channel work is serialised because
`show` is called faster than the round trip completes during playback, and
overlapping updates would swap visibility out of order and strobe.

Prefetching loads a window around the playhead, nearest first and forward
before backward, since playback moves forward and that frame is needed
soonest. `FrameCache` is byte-budgeted rather than entry-counted because frame
size tracks how much precipitation is on screen, and it evicts by distance from
the playhead: plain LRU would keep frames the prefetcher touched a moment ago
even after the playhead moved to the far end of the timeline.

Also adds DpcRadarSource, which reads published frames from our CDN and never
from the DPC API. Without it, the `dpc` adapter would have had to fall back to
mock, putting demo frames on screen under the label of live data — exactly the
confusion the adapter split exists to prevent. It now fails naming the missing
setting instead.

Running it on the emulator caught three things the tests had not:

- The notifier wrote to `state` from inside `build()`, which Riverpod rejects
  as an uninitialised provider. That broke startup, not just tests.
- Eight-month-old demo frames rendered as "Aggiornato 342535 minuti fa". The
  age formatter now steps up to hours and days.
- Demo mode sat permanently behind a stale-data warning and so never showed the
  working state it exists to demonstrate. MockRadarSource now shifts the
  bundled timestamps onto the present, leaving images, order and spacing
  untouched, so the timeline behaves exactly as it would on live data.

Corrects docs/stack-decisions.md, which described a disk cache that was not
built: mock frames already live in the asset bundle, so a disk layer belongs
with the network adapter where it would save a real request.

Verified: analyze clean, 129 tests passing, and on the emulator the loop
advances, wraps, and reports "Aggiornato ora".

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
2026-09-10 12:57:16 +02:00
co-authored by Claude Opus 5
parent 8ff8a903b8
commit 91f9ac0fbf
18 changed files with 1856 additions and 26 deletions
@@ -0,0 +1,125 @@
import 'dart:async';
import 'dart:typed_data';
import 'package:maplibre_gl/maplibre_gl.dart';
import '../../core/region/geo.dart';
/// Draws radar frames over the map, double buffered.
///
/// Two image sources alternate: while one is on screen the next frame is
/// uploaded into the other, then visibility swaps. Updating a single source in
/// place flickers, because the layer is briefly showing a half-written texture;
/// adding every frame as its own layer avoids that too but pins all of them in
/// GPU memory at once, and twenty 512×512 RGBA frames is about 80 MB. Two
/// buffers cost the same whether the timeline holds six frames or sixty.
class RadarOverlay {
RadarOverlay({required this.map, required GeoBounds bounds})
: _quad = LatLngQuad(
topLeft: LatLng(bounds.north, bounds.west),
topRight: LatLng(bounds.north, bounds.east),
bottomRight: LatLng(bounds.south, bounds.east),
bottomLeft: LatLng(bounds.south, bounds.west),
);
static const String _sourceA = 'nuvolari-radar-a';
static const String _sourceB = 'nuvolari-radar-b';
static const String _layerA = 'nuvolari-radar-layer-a';
static const String _layerB = 'nuvolari-radar-layer-b';
final MapLibreMapController map;
/// Corners of the published frames. The worker renders in EPSG:3857 cropped
/// to exactly this box, so the quad is exact and nothing is warped client
/// side.
final LatLngQuad _quad;
bool _attached = false;
bool _showingA = true;
String? _visiblePath;
/// Serialises platform-channel work. `show` can be called faster than the
/// round trip completes — during playback, or while scrubbing — and
/// overlapping updates would swap visibility out of order and strobe.
Future<void> _pending = Future<void>.value();
bool get isAttached => _attached;
/// The frame currently on screen, or null before the first one.
String? get visiblePath => _visiblePath;
/// Creates the sources and layers, showing [bytes] immediately.
///
/// Safe to call again after the style reloads: the previous layers are torn
/// down first.
Future<void> attach(String path, Uint8List bytes) => _serialise(() async {
if (_attached) await _detachUnsafe();
await map.addImageSource(_sourceA, bytes, _quad);
await map.addImageSource(_sourceB, bytes, _quad);
await map.addImageLayer(_layerA, _sourceA);
await map.addImageLayer(_layerB, _sourceB);
await map.setLayerVisibility(_layerB, false);
_attached = true;
_showingA = true;
_visiblePath = path;
});
/// Swaps [bytes] onto the map.
///
/// A no-op when [path] is already visible, so a rebuild that does not change
/// the playhead costs nothing.
Future<void> show(String path, Uint8List bytes) {
if (!_attached) return attach(path, bytes);
if (path == _visiblePath) return Future<void>.value();
return _serialise(() async {
final hiddenSource = _showingA ? _sourceB : _sourceA;
final hiddenLayer = _showingA ? _layerB : _layerA;
final visibleLayer = _showingA ? _layerA : _layerB;
// Upload first, reveal second: the new texture is complete before it is
// ever shown, which is what removes the flicker.
await map.updateImageSource(hiddenSource, bytes, null);
await map.setLayerVisibility(hiddenLayer, true);
await map.setLayerVisibility(visibleLayer, false);
_showingA = !_showingA;
_visiblePath = path;
});
}
/// Removes the layers and sources.
Future<void> detach() => _serialise(_detachUnsafe);
Future<void> _detachUnsafe() async {
// Layers reference sources, so they have to go first. Each removal is
// tolerated failing: the style may already have dropped them, and the goal
// here is to end up with nothing rather than to prove what was there.
for (final layer in <String>[_layerA, _layerB]) {
try {
await map.removeLayer(layer);
} on Object {
continue;
}
}
for (final source in <String>[_sourceA, _sourceB]) {
try {
await map.removeSource(source);
} on Object {
continue;
}
}
_attached = false;
_visiblePath = null;
}
Future<void> _serialise(Future<void> Function() action) {
final next = _pending.then((_) => action());
// Swallow the failure for the chain's sake only: a platform-channel error
// on one frame must not deadlock every later frame behind it.
_pending = next.catchError((Object _) {});
return next;
}
}