[Clock app] Time runs slower as expected

David can you confirm if this is also an issue when running the clock app in the desktop? I am unable to confirm this bug since I do not have a mobile device capable of running Ubuntu Touch.

I can't reproduce it on desktop...

Al 05/05/13 17:24, En/na Nekhelesh Ramananthan ha escrit:
> David can you confirm if this is also an issue when running the clock
> app in the desktop? I am unable to confirm this bug since I do not have
> a mobile device capable of running Ubuntu Touch.
>

Hi Nekhelesh,

It's not reproducible on the desktop, only on a device. Indeed, that's
why probably no one noticed until now.

Although someone from the SDK team who had a look at the code mentioned
that it might be reproducible on the desktop if the stopwatch is left
running for a long time. I haven't looked at the timer code, but it
seems there was a timing function that was on a linear path. I'll get
them to comment on the bug on Monday.

Cheers,
David.

Confirmed on a nexus 7. less pronounced on the nexus 4, but still apparent.

When stopwatch hundreds timer kicks, there is too much updated in StopwatchScript.increaseDecimal() function.

Try to use several timers, one for the hundreds and one for the seconds, and update the numbers for the hundreds and seconds separately. You most probably will need to drive this from a C++ plugin, where you update the UI asynchronously. Try to minimize the UI elements updated synchronously upon each timer kick, don't forget that these are done synchronously.

Here's a video showing stopwatch comparisions.. iOS, Android and Ubuntu Touch..

http://www.youtube.com/watch?v=nuE9R81ex-Q

Fix committed into lp:ubuntu-clock-app at revision 94, scheduled for release in ubuntu-clock-app, milestone coreapps-13.10-month-2