Skip to content

Conversation

@elnjensen
Copy link
Contributor

Small change to present the bolus controller after a carb entry on the watch only in cases where the bolus recommendation is non-zero. Always presenting the bolus interface even for zero recommended bolus could be considered as a form of carb entry confirmation, but it doesn't seem necessary with the success haptic now in place, and also doesn't seem consistent with the behavior in the phone app and the overall "assume success but alert on failure" approach of the rest of the UI.

@ps2 ps2 merged commit ad179b6 into LoopKit:dev Mar 6, 2019
@elnjensen elnjensen deleted the watch-nonzero-bolus branch July 13, 2024 23:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants