Skip to content

Adding VeryHigh Overview Display Option#4768

Open
vanmegen wants to merge 11 commits into
nightscout:devfrom
vanmegen:fmegen/dev-3.4.0.0
Open

Adding VeryHigh Overview Display Option#4768
vanmegen wants to merge 11 commits into
nightscout:devfrom
vanmegen:fmegen/dev-3.4.0.0

Conversation

@vanmegen
Copy link
Copy Markdown

@vanmegen vanmegen commented Apr 26, 2026

This is analog to the nightscout Very High setting which displays bg values higher than a configurable value in a different color.
I did set the default to 400, but it can be set to 240 to be a similar threshold as nightscout uses.

(in the following screenshot red dots mark values higher than 220)
image

I have added this to the overview settings
image

And added this to the startup-wizzard
image

Widgets are updated as well
image

And watchfaces
image
image
image

@vanmegen
Copy link
Copy Markdown
Author

Note, this is an updated version of PR #3678

fmegen added 2 commits April 27, 2026 10:59
… installs use the same thresholds and colors as the existing (this is important because the low_mark color has been changed to yellow instead of previously, red.)
@vanmegen
Copy link
Copy Markdown
Author

@olorinmaia, @Philoul @koelewij
Please consider this PR to continue our discussions

@koelewij
Copy link
Copy Markdown

To my opinion this is a change with minimal impact. If users don't want the extra range, they can set the limits to such a value that they still have the old behavior.
On the high range just set the red limit to max.
For the lower side just set both the same, so there is only red and no yellow.

@vanmegen
Copy link
Copy Markdown
Author

vanmegen commented May 4, 2026

@koelewij Thank you very much for your comment!

@olorinmaia , @Philoul @koelewij Sorry to ping again. I am just wondering that you are ok with this PR (as you helped with/commented) the original PR #3678 already.

kind regards,
friedel

@Philoul
Copy link
Copy Markdown
Contributor

Philoul commented May 6, 2026

@vanmegen
Sorry, I didn't had time to test your PR until now.

  • Reading comments and screenshots, a lot of work has been done to have the same BG colors everywhere, including into wizard and watch 👍

I will try to find time to test it to provide you my comments, but not sure very quickly 🥵...

@vanmegen
Copy link
Copy Markdown
Author

vanmegen commented May 8, 2026

Hi @Philoul,
thank you very much for your kind comments.

I just realized that I forgot to put screenshots for some additional places where the new UI displays blood sugar values

Insulin
image

Carbs
image

and the combination carbs/insulin dialog
image

kind regards,
friedel

fmegen added 4 commits May 16, 2026 17:38
# Conflicts:
#	plugins/sync/src/main/kotlin/app/aaps/plugins/sync/wear/wearintegration/DataHandlerMobile.kt
#	workflow/src/main/kotlin/app/aaps/workflow/PrepareBgDataWorker.kt
#	workflow/src/main/kotlin/app/aaps/workflow/PrepareBucketedDataWorker.kt
@sonarqubecloud
Copy link
Copy Markdown

@Philoul
Copy link
Copy Markdown
Contributor

Philoul commented May 19, 2026

I tested it on my dev phone, here are my different comments:
Concerning very low:

  1. default value and minimum value should be set to 39 mg/dl (or 25 ???).
  • AAPS don't manage values lower than 39 and I was surprised to see 25 as minimum in current OverviewLowMark double key, and 72 for default and not 70... (@MilosKozak an error or is it intended?)
  • Default value for VeryLow should be aligned to the minimum value to not change default colors (by default very low override low if the very low value is above low value)
  1. I think within User Interface Maximum value for VeryLow should be equal to the selected Low Value (and hardcoded within OverviewVeryLowMark (maxMgdl) to 72 (or 70) and not 160 mg/dl
  • The user should not be able to select an higher value for very low compared to low, and same constraint for Very High that should always be above or equal high value

Concerning the Very High maximum and default value, it should be the maximum allowed value (I don't remember if it's 380 or 400 mgdl...)

By default, if this feature is included, it should be "transparent" for users: they will have enough new things just with the new UI, so I don't think we should add something additional visible. Then those who will want to adjust settings to see very high and Very Low will be able to adjust settings accordingly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants