Files
dmc/app/lib/ui/providers/mission_meta_provider.dart
T
Constantin LeueandClaude Sonnet 5 35351140ae Persist the ground elevation profile with the mission
The Mini-Altitude-Profile terrain data only ever lived in TerrainNotifier's
in-memory state (one slot, keyed by route). Every app restart, or every
switch away from and back to a mission, forced a full re-fetch of all
AWS Terrarium elevation tiles for the route - the noticeably slow load
the user reported for some missions was this happening on every visit,
not just once.

Adds a nullable terrainProfileJson column to the missions table
(schema v6->v7) and a saveTerrainProfile() repository method, kept
separate from the regular waypoint upsert() so an ordinary autosave never
clobbers an already-cached profile. TerrainNotifier persists a profile
right after a successful fetch (fire-and-forget) and gains restore(),
called from CurrentMissionMetaNotifier whenever a mission is loaded/
started so a previously fetched profile is available immediately -
ensureFor() still validates its routeKey before use, so a stale restored
profile is never shown for a route that has since changed.

Also included in mission export/import (MissionExportData/
ParsedMissionImport) so sharing a mission carries its terrain cache along
instead of forcing the recipient to refetch it.

Sample-count/resolution stays as-is for now (still fixed 30m spacing,
10-2000 samples) - adapting the sampling density to terrain variance
(e.g. coarser sampling over flat ground) is a separate follow-up.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-08-04 08:10:41 +02:00

158 lines
6.1 KiB
Dart

import 'dart:async';
import 'package:flutter_riverpod/flutter_riverpod.dart';
import '../../domain/waypoint/flat_waypoint_list.dart';
import 'current_mission_provider.dart';
import 'database_provider.dart';
import 'follow_drone_provider.dart';
import 'map_controller_provider.dart';
import 'terrain_provider.dart';
/// Metadaten der aktuell in Bearbeitung befindlichen Mission - ergaenzt
/// currentMissionProvider (das nur die Wegpunkte haelt) um Name/Ort und die
/// Datenbank-id, sobald die Mission mindestens einmal gespeichert wurde.
class MissionMeta {
const MissionMeta({this.id, this.name = 'New mission', this.placeName});
/// Null, solange die Mission noch nie (auto-)gespeichert wurde.
final int? id;
final String name;
final String? placeName;
MissionMeta copyWith({int? id, String? name, String? placeName}) {
return MissionMeta(
id: id ?? this.id,
name: name ?? this.name,
placeName: placeName ?? this.placeName,
);
}
}
/// Haelt Name/id der aktuellen Mission und autosaved sie ueber
/// MissionRepository (Doku 7.5), sobald sich die Wegpunktliste aendert -
/// analog scheduleAutosave()/flushPendingAutosave() im HTML-Demonstrator
/// (dort 800ms debounce, hier identisch uebernommen).
class CurrentMissionMetaNotifier extends Notifier<MissionMeta> {
Timer? _autosaveTimer;
bool _suppressAutosave = false;
@override
MissionMeta build() {
ref.listen(currentMissionProvider, (previous, next) {
if (!_suppressAutosave) _scheduleAutosave();
});
ref.onDispose(() => _autosaveTimer?.cancel());
return const MissionMeta();
}
/// Laedt die zuletzt bearbeitete Mission (falls vorhanden) beim App-Start
/// wieder, damit ein Autosave-Draft einen Neustart ueberlebt (Doku 7.5).
Future<void> restoreLastSession() async {
final settings = await ref.read(appSettingsRepositoryProvider).load();
final missionId = settings.currentMissionId;
if (missionId == null) return;
final loaded = await ref.read(missionRepositoryProvider).load(missionId);
if (loaded == null) return;
_suppressAutosave = true;
ref.read(currentMissionProvider.notifier).replaceAll(loaded.waypoints);
_suppressAutosave = false;
state = MissionMeta(id: missionId, name: loaded.name, placeName: loaded.placeName);
ref.read(terrainProvider.notifier).restore(loaded.terrainProfile);
_fitMapToWaypoints(loaded.waypoints);
}
/// Analog startNewMission() im HTML-Demonstrator: sichert zuerst noch
/// ausstehende Aenderungen der bisherigen Mission, dann leerer Neustart.
Future<void> startNew() => _startNew(const MissionMeta());
/// Analog setMissionFromPlace() im HTML-Demonstrator: eine Ortssuche (oder
/// GPS-Ortung) beginnt immer eine neue, leere Mission, benannt nach dem
/// gefundenen Ort - nicht nur ein Kartensprung.
Future<void> startNewFromPlace(String label) =>
_startNew(MissionMeta(name: label, placeName: label));
Future<void> _startNew(MissionMeta newState) async {
await _flushNow();
_suppressAutosave = true;
ref.read(currentMissionProvider.notifier).replaceAll(const []);
_suppressAutosave = false;
state = newState;
ref.read(terrainProvider.notifier).restore(null);
await ref.read(appSettingsRepositoryProvider).setCurrentMissionId(null);
}
Future<void> loadMission(int id) async {
await _flushNow();
final loaded = await ref.read(missionRepositoryProvider).load(id);
if (loaded == null) return;
_suppressAutosave = true;
ref.read(currentMissionProvider.notifier).replaceAll(loaded.waypoints);
_suppressAutosave = false;
state = MissionMeta(id: id, name: loaded.name, placeName: loaded.placeName);
ref.read(terrainProvider.notifier).restore(loaded.terrainProfile);
_fitMapToWaypoints(loaded.waypoints);
await ref.read(appSettingsRepositoryProvider).setCurrentMissionId(id);
}
/// Zentriert die Karte auf die geladene Mission (Doku 3.6) - ohne dies
/// bliebe die Kamera an der zuletzt betrachteten Stelle stehen, waehrend
/// eine voellig andernorts gelegene Mission angezeigt wird. Analog
/// fitToWaypoints() im HTML-Demonstrator bzw. _onFitPressed() in
/// MapSearchControls, hier aber automatisch statt nutzerausgeloest -
/// nutzt dieselbe Padding-Logik wie der manuelle Fit-Button
/// (fitMapControllerToWaypoints), damit beide nicht wieder auseinander-
/// laufen koennen.
///
/// Beendet dabei ebenfalls den Kartenfolgemodus (followDroneProvider,
/// Doku 3.11, siehe fitMapToWaypoints in map_controller_provider.dart) -
/// das Laden einer anderen Mission waehrend des Verfolgens soll auf der
/// neuen Mission stehen bleiben, nicht sofort wieder zur Drohne springen.
void _fitMapToWaypoints(List<Waypoint> waypoints) {
ref.read(followDroneProvider.notifier).set(false);
fitMapControllerToWaypoints(ref.read(mapControllerProvider), waypoints);
}
/// Benennt eine gespeicherte Mission um (Doku 3.6: nur ueber die
/// Missionsliste moeglich, dort hat jede Zeile immer bereits eine id).
/// Aktualisiert zusaetzlich den eigenen Zustand, falls [id] die gerade
/// aktive Mission ist.
Future<void> renameMission(int id, String name) async {
await ref.read(missionRepositoryProvider).rename(id, name);
if (state.id == id) {
state = state.copyWith(name: name);
}
}
void _scheduleAutosave() {
if (ref.read(currentMissionProvider).isEmpty) return;
_autosaveTimer?.cancel();
_autosaveTimer = Timer(const Duration(milliseconds: 800), () {
unawaited(_flushNow());
});
}
Future<void> _flushNow() async {
_autosaveTimer?.cancel();
_autosaveTimer = null;
final waypoints = ref.read(currentMissionProvider);
if (waypoints.isEmpty) return;
final id = await ref.read(missionRepositoryProvider).upsert(
id: state.id,
name: state.name,
placeName: state.placeName,
waypoints: waypoints,
);
if (state.id == null) {
state = state.copyWith(id: id);
}
await ref.read(appSettingsRepositoryProvider).setCurrentMissionId(id);
}
}
final currentMissionMetaProvider =
NotifierProvider<CurrentMissionMetaNotifier, MissionMeta>(
CurrentMissionMetaNotifier.new);