comparison Discovery/Src/tMenuEditHardware.c @ 814:26ae9e8f24fd

Dev Bugfix: O2 values of new detected sensors were shown as invalid: In the previous version sometime O2 values were shown as invalid (red) after a autodetection cycle was run. After sleep/wakeup cycle the status were shown correct. Rootcause was that the out of bounds detection is based on the divesettings while the HW menu were only updating the common settings regarding active / inactive sensors. The problem has been solved by adding an divesettings update within the HW / sensor menu.
author Ideenmodellierer
date Sun, 03 Sep 2023 17:58:12 +0200
parents 1e3c12d772eb
children ffb1036c27c2
comparison
equal deleted inserted replaced
813:1e688b630a6e 814:26ae9e8f24fd
592 } 592 }
593 else 593 else
594 { 594 {
595 write_field_on_off(StMHARD3_O2_Sensor3, 30, 95, ME_Y_LINE3, &FontT48, "", sensorActive[2]); 595 write_field_on_off(StMHARD3_O2_Sensor3, 30, 95, ME_Y_LINE3, &FontT48, "", sensorActive[2]);
596 } 596 }
597
598 stateRealGetPointerWrite()->diveSettings.ppo2sensors_deactivated = pSettings->ppo2sensors_deactivated;
599
597 if(settingsGetPointer()->ppo2sensors_deactivated & 1) 600 if(settingsGetPointer()->ppo2sensors_deactivated & 1)
598 sensorActive[0] = 0; 601 sensorActive[0] = 0;
599 if(settingsGetPointer()->ppo2sensors_deactivated & 2) 602 if(settingsGetPointer()->ppo2sensors_deactivated & 2)
600 sensorActive[1] = 0; 603 sensorActive[1] = 0;
601 if(settingsGetPointer()->ppo2sensors_deactivated & 4) 604 if(settingsGetPointer()->ppo2sensors_deactivated & 4)