to avoid adding extra menu lines, use an enum to track the TIR type chosen and allow the user to just chose directly, or cycle through by double-tapping the statistics view
Removed old TIR option based on user-set values in favor of the newer "Time in Tight Range" method.
Two options are now:
- standardized TIR (70-180mg/dL)
- newer TITR (70-140mg/dL)
- https://diatribe.org/time-tight-range-new-diabetes-goal
- added double tap gesture to the statistics view to quickly change between both types.
-
- added transition so that the user is visually shown which limits are changed when changing types
- added localization. Initial translations for EN, ES.
- changed many of the settings menu row descriptions to remove the "?" from them to clean up the look of them.
As the row label and text field have different and consistent formats (bold/colour), it can be implicitly seen that a given label applies to a given field/option so there's no real need to use a colon at the end.
By removing the colon from the string, we can also use them for titles etc without it looking strange
Whilst most labels previously had colons, many were missing which can give the UI a confusing look
Update Main.storyboard
- change "Follow Dexcom-app" to "Read from Dexcom app" to avoid confusion with Dexcom Follow
- changes to transmitter/sensor display formats to use Nightscout format and improve clarity
- label changes
- typo correction: disclosureAaccessoryView -> disclosureAccessoryView
- simplified sensor status UIAlert and now includes sensor duration (elapsed time since start) and remaining (time until end date)
* New translations AlertTypesSettingsView.strings (French)
* New translations M5StackView.strings (Spanish)
* New translations M5StackView.strings (German)
* New translations M5StackView.strings (Dutch)
* New translations Main.strings (French)
* New translations Main.strings (Spanish)
* New translations Main.strings (Arabic)
* New translations Main.strings (German)
* New translations Main.strings (Finnish)
* New translations Main.strings (Dutch)
* New translations Main.strings (Portuguese)
* New translations Main.strings (Swedish)
* New translations LibreStates.strings (Arabic)
* New translations LibreNFC.strings (German)
* New translations LibreNFC.strings (Finnish)
* New translations LibreNFC.strings (Dutch)
* New translations LibreNFC.strings (Portuguese)
* New translations LibreStates.strings (French)
* New translations LibreStates.strings (Spanish)
* New translations LibreStates.strings (German)
* New translations LibreStates.strings (Finnish)
* New translations LibreStates.strings (Dutch)
* New translations LibreStates.strings (Swedish)
* New translations LibreStates.strings (English)
* New translations Main.strings (English)
* New translations SpeakReading.strings (French)
* New translations SpeakReading.strings (Spanish)
* New translations SpeakReading.strings (German)
* New translations SpeakReading.strings (Dutch)
* New translations WatlaaView.strings (French)
* New translations WatlaaView.strings (German)
* New translations WatlaaView.strings (Finnish)
* New translations SettingsViews.strings (Arabic)
* New translations NightScoutTestResult.strings (German)
* New translations SettingsViews.strings (French)
* New translations SettingsViews.strings (Spanish)
* New translations SettingsViews.strings (German)
* New translations SettingsViews.strings (Finnish)
* New translations SettingsViews.strings (Dutch)
* New translations SettingsViews.strings (Portuguese)
* New translations SettingsViews.strings (Swedish)
* New translations SettingsViews.strings (English)
* New translations Snooze.strings (Spanish)
* New translations Snooze.strings (Arabic)
* New translations Snooze.strings (German)
* New translations LibreNFC.strings (Arabic)
* New translations LibreNFC.strings (French)
* New translations BluetoothPeripheralsView.strings (German)
* New translations BluetoothPeripheralView.strings (Dutch)
* New translations CalibrationRequest.strings (German)
* New translations CalibrationRequest.strings (Portuguese)
* New translations Alerts.strings (Spanish)
* New translations AlertTypesSettingsView.strings (Arabic)
* New translations AlertTypesSettingsView.strings (German)
* New translations AlertTypesSettingsView.strings (Dutch)
* New translations AlertTypesSettingsView.strings (Swedish)
* New translations AlertTypesSettingsView.strings (English)
* New translations Alerts.strings (French)
* New translations BluetoothPeripheralView.strings (German)
* New translations Alerts.strings (German)
* New translations BluetoothPeripheralView.strings (French)
* New translations BluetoothPeripheralView.strings (Spanish)
* New translations Common.strings (French)
* New translations HomeView.strings (Spanish)
* New translations HomeView.strings (German)
* New translations HomeView.strings (Dutch)
* New translations LibreErrors.strings (French)
* New translations LibreErrors.strings (Spanish)
* New translations LibreErrors.strings (German)
* New translations Common.strings (Spanish)
* New translations Common.strings (Arabic)
* New translations Common.strings (German)
* New translations Common.strings (Finnish)
* New translations Common.strings (Dutch)
* New translations Common.strings (Portuguese)
* New translations Common.strings (Swedish)
* New translations Common.strings (English)
* New translations DexcomShareTestResult.strings (Arabic)
* New translations ErrorMessages.strings (German)
* New translations DexcomShareTestResult.strings (German)
* New translations ErrorMessages.strings (French)
* New translations ErrorMessages.strings (Arabic)
* New translations BluetoothPeripheralView.strings (Swedish)
For two reasons :
- Dexcom share response is not always giving the right error code, for example if initial value in the settings is done with random account and random password, then Dexcom does not say if it's the account or password that is wrong
- it's simply not secure to say if it was the account or password that is wrong
And moved the string to TextsCommon as it may apply to other providers as well (never know)
Following instructions are copied from Spike :
On your Apple Watch or the Watch app in your iOS device select the
"Modular" watch face and make sure you also select the "Calendar Complication" to be present in the middle of the watch face
Your glucose values should now start syncing to your watch when you receive your next reading from your CGM transmitter.
If by any chance you're not getting readings in your Apple Watch, go to the Watch app and under "General", "Reset"
click the "Reset Sync Data" and wait a few minutes.
Paul Plant