Why only this one alarm? I think wherever possible, we want to be more general about alarm user actions. If user chooses to end treatment in response to any alarm that didn't block that option, we should allow it.
I looked at struct's bytes size method. I made this function because the byte size should not be assumed in anyways, otherwise, the data will not be mapped correctly to the firmware structures.
There is one use case with the manual BP / HR entry where the keyboard is kept visible after the user presses 'Enter'. This allows the focus to move from systolic -> diastolic -> HR automatically without causing it to flash invisible and then visible. So at the time it was left it up to the developer of the component to decide when to minimize the keyboard in case it would need to stay up as they kept moved between input fields.
If we remove automatically transitioning from one input field to the next in the manual BP / HR entry pop up, then I'd say there's no reason not to hide the keyboard inside the TextEntry component when Enter is pressed.
Recently I'm removing the "Response" from the log's "infoText" function, since the log already has the source we will see it is coming from HD/DG and it make the "Response" useless and gets more space only. Please apply the same for the DG. And don't forget to update the doxygen comment as well.
