What happens: On the SmartMTR meter with Show values = Extremes, the min/max value numbers disappear after ~a second while their triangle markers are still visible. They should track each other.
Expected: The value numbers stay visible as long as the markers, at the same opacity — fade and disappear together.
Root cause: Both already compute the same extremesOpacity() and share the < 0.02 cutoff, so the alpha is identical — but the value display is under-driven vs. the triangle: the connector line and unit text are dimmed to opacity × 0.55 (kUnitDim, src/gui/VfoWidget.cpp:3503 and :3529), and small haloed text loses legibility at an opacity where the solid bright triangle is still clearly visible. So the numbers read as vanishing early.
Proposed fix: Let the value text/connector fade on the same effective curve as the marker (drop/raise the kUnitDim attenuation and/or a small legibility floor on the number), keeping extremesOpacity() as the single source of truth. Localized to drawSmartMtrLabels() / extremeLabels(); no change to the opacity math, window/speed tuning, or the S-meter path.
Repro: SmartMTR view → Show values = Extremes → live signal → trigger a peak/null and watch it decay.
Introduced with #3723.
What happens: On the SmartMTR meter with Show values = Extremes, the min/max value numbers disappear after ~a second while their triangle markers are still visible. They should track each other.
Expected: The value numbers stay visible as long as the markers, at the same opacity — fade and disappear together.
Root cause: Both already compute the same
extremesOpacity()and share the< 0.02cutoff, so the alpha is identical — but the value display is under-driven vs. the triangle: the connector line and unit text are dimmed toopacity × 0.55(kUnitDim,src/gui/VfoWidget.cpp:3503and:3529), and small haloed text loses legibility at an opacity where the solid bright triangle is still clearly visible. So the numbers read as vanishing early.Proposed fix: Let the value text/connector fade on the same effective curve as the marker (drop/raise the
kUnitDimattenuation and/or a small legibility floor on the number), keepingextremesOpacity()as the single source of truth. Localized todrawSmartMtrLabels()/extremeLabels(); no change to the opacity math, window/speed tuning, or the S-meter path.Repro: SmartMTR view → Show values = Extremes → live signal → trigger a peak/null and watch it decay.
Introduced with #3723.