From 0adab74255047755cd889a26b39f2581f688d4c4 Mon Sep 17 00:00:00 2001 From: Silvano Seva Date: Tue, 12 Sep 2023 11:39:51 +0200 Subject: [PATCH] M17: workaround to avoid UI glitches when a new dst callsign is set. When a new dst callsign is set, the rtx configuration data structure is updated and this may trigger false setting of the lsfOk variable to true, causing the M17 info screen to appear for a very small, but noticeable, amount of time. --- openrtx/src/rtx/OpMode_M17.cpp | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/openrtx/src/rtx/OpMode_M17.cpp b/openrtx/src/rtx/OpMode_M17.cpp index e8353206..eb8e9029 100644 --- a/openrtx/src/rtx/OpMode_M17.cpp +++ b/openrtx/src/rtx/OpMode_M17.cpp @@ -75,7 +75,16 @@ void OpMode_M17::disable() void OpMode_M17::update(rtxStatus_t *const status, const bool newCfg) { - (void) newCfg; + // + // FIXME: workaround to avoid UI glitches when a new dst callsign is set. + // + // When a new dst callsign is set, the rtx configuration data structure is + // updated and this may trigger false setting of the lsfOk variable to true, + // causing the M17 info screen to appear for a very small, but noticeable, + // amount of time. + // + if(newCfg) + status->lsfOk = false; #if defined(PLATFORM_MD3x0) || defined(PLATFORM_MDUV3x0) //