Conversation
|
you must create new string if param is different otherwise it crash |
|
and I checked only this one example ... |
|
Here this string is not only used for reservoir level, but also for TDD (with a max TDD).
Additional question: how far we standardize information provided in pump overview
I found customization of information on several other "standard" items like reservoir level (with or without max), TDD (with or without max TDD), extended boluses (rate, delivered amount? timing?...)
|
|
I'd standartize it everywhere. easier to maintain |
|
I started to standardize common pump information (first with lastBolus including ago)
|
# Conflicts: # pump/combov2/src/main/kotlin/info/nightscout/pump/combov2/ComboV2Fragment.kt # pump/insight/src/main/kotlin/app/aaps/pump/insight/InsightFragment.kt
|
With my latest commit here are the proposed harmonisation pour Reservoir Level and TDD:
|
|



Update Pump Overview with some missing ch (Virtual, Dash, Eros, Dana, Equil, EOPatch, Medtronic)
One question concerning the formating included into translated strings:
%1$.2fU/hby%1$s, I think translated strings (with previous format) should be replaced by the english one until a new translation is done in Crowdin?If not we have a risk of crash... (I can update my PR with another key to prevent this)