Today scope updates when view switched

[LionelB]

With the installation of OTA 3.5, new behaviour of the Today scope. Just going back to the Today scope from the 'concertina' view triggers a refresh of the scope, every time. This happens without pulling down to refresh.

Unwelcome if this uses data without being requested !

[Chris Wayne (cwayne)]

This was intended behavior, to ensure that the date was refreshed correctly, and that all of the data shown is up to date (reveieved calls/texts/etc). We can possibly look into tweaking exactly how often this is refreshed to possibly lower any data cost

[LionelB (retweet)]

I can see the virtue of that. The effect will vary according to how much a user utilises the ‘concertina’ mode. It is a useful navigation tool.

Rather than ‘refresh on every fifth return’, better ‘refresh no more than once an hour’.

Ideally, user settings to limit how a user wants it to work. Maybe the simplest is to have a ‘do not refresh when on data’ option ?

> On 13 May 2015, at 12:12, Chris Wayne <email address hidden> wrote:
>
> This was intended behavior, to ensure that the date was refreshed
> correctly, and that all of the data shown is up to date (reveieved
> calls/texts/etc). We can possibly look into tweaking exactly how often
> this is refreshed to possibly lower any data cost

[Chris Wayne (cwayne)]

That would be ideal yes, but that's unfortunately not up to the scope, but to the scope framework. Really all we can do as scope authors is pick the right time-frame for auto-refreshing, and perhaps we chose too aggresively on this update

[LionelB (retweet)]

Whatever the outcome, the ability of users to give feedback and be heard is 10,000% better than any other OS!

Good luck and keep up the good work.

> On 13 May 2015, at 12:57, Chris Wayne <email address hidden> wrote:
>
> That would be ideal yes, but that's unfortunately not up to the scope,
> but to the scope framework. Really all we can do as scope authors is
> pick the right time-frame for auto-refreshing, and perhaps we chose too
> aggresively on this update

[Chris Wayne (cwayne)]

Thanks, and thank you for the feedback, I think we might be able to knock it down a bit to refresh less often :) Will keep this bug updated

[LionelB (retweet)]

btw the local ‘railway station’ closed in 1962. Wiki history feeding into transport … :-)

> On 13 May 2015, at 13:28, Chris Wayne <email address hidden> wrote:
>
> Thanks, and thank you for the feedback, I think we might be able to
> knock it down a bit to refresh less often :) Will keep this bug updated

[themeles (themeles)]

I'm also a bit fed up with this behaviour: I quickly want to check what I have to do today and it's starts loading and loading and loading....

[LionelB (retweet)]

I have deactivated the Today scope until a fix. Almost any action sends the scope into manic refresh mode. It is even more intrusive than I first thought.

[TenLeftFingers (tenleftfingers)]

Would it be possible to simply timestamp when the last refresh was performed and short-circuit any further refreshes if the today_sunrise <= timestamp && today_sunset >= timestamp? This would guarantee only one refresh per day.

Another consideration for this isn't just data, but performance, as mentioned in comment #7. This scope is rarely 'ready' when the user needs it. I think this bug may also be a candidate for the Today scope as regards unnecessary updating: https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1466669

But I'll let someone more knowledgeable than me decide whether to assign or not.

[Pim van Nierop (pim-van-nierop)]

Yes, I agree with this being undesired behaviour. Takes the speed out of user experience especially on poor network connections.

[Cédric Bellegarde (gnumdk)]

Horrible behaviour, removing this scope for now...

A scope can't do refresh in background and refresh widgets on the fly? This look so 90's...

Is this a limitation in scope framework? (that really need to be fixed).

[Kyle Nitzsche (knitzsche)]

With the upcoming release of Today, we have switch the auto refresh from a setting that means "refresh in minutes" to "refresh in about an hour".

[Yuan-Chen Cheng (ycheng-twn)]

@kyle, I guess we already release before ota6 ?

[Kyle Nitzsche (knitzsche)]

Yes. The auto refresh (aka "ResultsTtlType" key) in the scope ini card [1] populated from make-install var [2] has been set to "Large" (which means refresh in about an hour) for some time, certainly since before OTA6.

[1] http://bazaar.launchpad.net/~todayscope-team/today-scope/trunk/view/head:/click-src/aggregator/scope.ini.in.in
[2] http://bazaar.launchpad.net/~todayscope-team/today-scope/trunk/view/head:/make-click.sh#L28