-
Notifications
You must be signed in to change notification settings - Fork 118
Release/3.1.1 #19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release/3.1.1 #19
Conversation
* Implemented UI design from Kate F * New battery indicator from Jon M * Bigger fonts in general, especially for time * New special value icons instead of special value numbers (??? instead of "10") * Switched black and white backgrounds, to improve readability * New space for T1D name * Made JS faster based on inputs from John C and Christine D, to help with reliability and refresh problems * New "two time" fix, to quickly diagnose refresh problem (when pebble app has crashed or gotten lost) * Time and date are from system, so always up to date and watch can function like a watch * More descriptive error messages * Implemented bug fixes, especially for Rajat build users * Commented code in much greater detail * Will publish FAQ to quickly identify problems and address faster
UI changes (Kate F), New Features, Other Fixes
…ld and the directionToTrand mapping; some reformatting
… still isn't right logo isn't showing now
… pebble is offline
…; start passing reading timestamp to c code
…ide the value so it's clear that the data isn't current
… info on the pebble, not perfect, but better
UI changes (Kate F), New Features, Other Fixes
|
As requested added to release PR from another thread.
Today the pebble connection appeared fine but the value displayed was not the latest bg value (my wife is running the old version on old website during this testing phase so I was able to get updated data from her). I checked the /pebble link on the azure site (new version) and that was updating correctly. There is no indication of an error on the pebble it gives a value and states says "3 mins ago".However whilst the time is updating it remains stuck on 3 mins ago even when there has been two other readings displayed on the website and the /pebble link. It did update ok when I moved off and then back on the watchface. I hope I have explained issues clearly but if you need me to clarify anything or want me to try something to better diagnose issue then let me know. Grant |
|
Closing, as v4.0.0 is more or less a clean start and wraps much of this work up. |
Also: