system.getTimer() on Android

http://developer.anscamobile.com/reference/index/eventtype-0


In the simulator, this corresponds to the simulator running in the background.

and

On the simulator, this occurs when the simulator was in the background and now is the foreground application.
[import]uid: 44812 topic_id: 14768 reply_id: 54758[/import]

This bug is not present in the simulator:

Suspended at 6334.00, wall 09/07/11 15:14:50
Resumed at 6335.00, slept 1.00ms, wall time: 09/07/11 15:56:06

[import]uid: 44812 topic_id: 14768 reply_id: 54762[/import]

Hello Brian,

The issue was indeed caused by overflow. In fact, it’s been overflowing (consistently) from the start and this overflow issue only became apparent after long suspensions. A time_t value was wrongly assumed to be 64-bit in the code. We just fixed it today. We also modified it to be unaffected by clock changes. So, now this function should never go backwards. Huzzah!

The fix will be made available in the next daily build, which is available to you if you are a paid subscriber. Keep a look out for daily build release notes stating fixes in system.getTimer().

Again, thanks for your help! Your test results helped us narrow down the issue. [import]uid: 32256 topic_id: 14768 reply_id: 54787[/import]

Great to hear, glad I could help!
[import]uid: 44812 topic_id: 14768 reply_id: 54799[/import]