You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have no idea what's involved in something like this or what your plans for updated Watch support are, but I think it would be awesome to draw the Predicted Glucose chart in the lower 2/3rds of the Loop app's main screen, just to understand how your number is going to get to the "Eventually" value.
@paulforgione that was always the end goal for that large black area 😄
watchOS 3 added support for SpriteKit, which I was planning to learn and then tackle the watch graph. hopefully someone can take up that call post-1.0!
@tomasboudr adding additional complications should be a relatively straightforward coding exercise, since all the communication and update mechanics are in place.
Activity
tomasboudr commentedon Sep 21, 2016
This will be awesome.
Would also love support for the Utilitarian Small complication (for use in the corner when using the simple or utility watch face)
Or for the Module Large face complication so that we can include the current bg, the predicted bg, and the last updated time.
CrushingT1D commentedon Sep 30, 2016
wonder if timing can be optimized with when watch is charging as opposed to a set time of day that may differ by person.
paulforgione commentedon Sep 30, 2016
I have no idea what's involved in something like this or what your plans for updated Watch support are, but I think it would be awesome to draw the Predicted Glucose chart in the lower 2/3rds of the Loop app's main screen, just to understand how your number is going to get to the "Eventually" value.
Visualized below:


loudnate commentedon Sep 30, 2016
@paulforgione that was always the end goal for that large black area 😄
watchOS 3 added support for SpriteKit, which I was planning to learn and then tackle the watch graph. hopefully someone can take up that call post-1.0!
@tomasboudr adding additional complications should be a relatively straightforward coding exercise, since all the communication and update mechanics are in place.
Using the crown sequencer directly for carb/bolus input
Using the crown sequencer directly for carb/bolus input (#203)
[LOOP-1664] Update bolus screen UI (#173)