Skip to content

Improve the Status Widget to update in real time as Loop data changes #320

Closed

Description

@bharat

Currently, the status widget only updates when it first appears. It should continue to update in real time as the Loop app detects changes and makes adjustments.

Activity

  1. bharat commented on Dec 23, 2016

    @bharat
    Author

    Looks like this might be non-trivial:

    1. http://stackoverflow.com/questions/28736506/kvo-with-shared-nsuserdefaults-in-swift
    2. http://www.atomicbird.com/blog/sharing-with-app-extensions

    MMWormhole might work for us:
    https://github.com/mutualmobile/MMWormhole

    Pulling in a new framework for this seems heavy. Alternatively, it might just be easiest to have the extension poll every minute. It's not like the data changes that quickly.

  2. ps2 commented on Dec 24, 2016

    @ps2
    Collaborator

    Could you update the description to describe the issue being solved?

  3. changed the title [-]Status widget - use key-value observing to update in real time[/-] [+]Improve the Status Widget to update in real time as Loop data changes[/+] on Dec 24, 2016
  4. bharat commented on Dec 24, 2016

    @bharat
    Author

    done. lmk if it needs more clarity.

  5. ps2 commented on Dec 24, 2016

    @ps2
    Collaborator

    So this is only an issue if you keep the status screen up for a while. Each time you bring it up it's is still refreshing correctly?

  6. bharat commented on Dec 24, 2016

    @bharat
    Author

    That is correct. So IMO it's not a critical issue, but if you happen to stay on the status screen for a while you might be looking at expired data. For what it's worth, it also shows the timestamps for all readings so you'd at least have a visual way of knowing that it's out of date, but date stamps are subtle.

  7. marionbarker commented on Sep 1, 2021

    @marionbarker
    Contributor

    I can't make the widget stay up long enough to test this. It does refresh each time I call it up.
    Can this issue be closed?

  8. github-actions commented on Nov 27, 2023

    @github-actions

    This issue is stale because it has been open for 30 days with no activity.

  9. github-actions commented on Dec 11, 2023

    @github-actions

    This issue was closed because it has been inactive for 14 days since being marked as stale.

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions