alarmVolumeTemp is the temporary volume being selected by the user while they are adjusting. alarmVolume is the kept alarm volume when the user exits the alarm volume screen. alarmVolume is set to alarmVolumeTemp only if the user hits confirm Upon confirm, alarmVolume is updated to be the same value as alarmVolumeTemp and is then sent down to the HD. Upon back / cancel, alarmVolume is left unchanged and is sent down to the HD to undo the temporary setting FW does not expose a play alarm volume without set message so we have to set the volume each time it is played for the user while they are adjusting.
Dara to refactor the POST test for RTC vs. processor timer so that we expect 1000 ms of processor time after RTC second changes. He and I have discussed this needed change.
FALSE is simply zero and TRUE is one. In case a boolean is somehow corrupted to something other than 1 or 0, I like to err on the side of safety. So the way I have it now, if isBloodPumpRunning() gets corrupted to > 1, it will consider that the pump is not running which is the safer thing to do.
If using a "==" comparison operator, I like to put the literal first so that the compiler will error if I accidentally use "=" instead. Otherwise, I like to put the literal last because it reads better.
There is no todo or fix for this. It is a hint for developers to be careful when using this in debugging since it affects the performance. Added more clarification.
