Skip to content

Commit f0eab57

Browse files
eriedclaude
andcommitted
fix(hud): lock-lost dot on GPS speed/coords only, not battery
Keep the lock-lost dot on the metrics that actually lose data on a GPS lock loss (external + phone GPS speed, GPS coordinates); drop it from the external-GPS battery tile so that stays a clean, persistent readout. The dot still clears the moment a good fix returns. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01GADLyChheAoMX9dQbRgRnH
1 parent ba55923 commit f0eab57

1 file changed

Lines changed: 5 additions & 5 deletions

File tree

hud/src/main/java/com/eried/eucplanet/hud/overlay/OverlayElements.kt

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -97,12 +97,12 @@ fun OverlayElementRenderer(element: OverlayElement, data: StudioElementData) {
9797

9898
// ---------- DATA_VALUE --------------------------------------------------
9999

100-
/** GPS-fix-dependent metrics show a lock-lost dot when their source has no fix
101-
* (box/phone connected but not locked). Battery is included on purpose: it now
102-
* keeps showing through a lock loss, so the dot is how the rider still sees the
103-
* external box lost its lock. */
100+
/** Speed + coordinate GPS metrics show a lock-lost dot when their source is
101+
* connected but has no fix; it clears the moment a good fix returns. Battery is
102+
* deliberately NOT dotted - it stays a clean, persistent readout (the whole
103+
* point of the battery fix), and the speed/coordinate tiles carry the cue. */
104104
private fun StudioMetric.gpsLockLost(data: StudioElementData): Boolean = when (this) {
105-
StudioMetric.EXTERNAL_GPS_SPEED, StudioMetric.EXTERNAL_GPS_BATTERY -> !data.externalGpsHasFix
105+
StudioMetric.EXTERNAL_GPS_SPEED -> !data.externalGpsHasFix
106106
StudioMetric.GPS_SPEED, StudioMetric.GPS -> !data.gpsHasFix
107107
else -> false
108108
}

0 commit comments

Comments
 (0)