Timer - add failed (in set)!

[amao-cbw]

Build environment: Windows
Moddable SDK version: 8.2.0
Target device: Desktop simulator

Description
I've noticed that timers will fail to create when the timeout length is 1 hour. Is this expected behaviour? If so, what are the timer limitations? I didn't see anything about this in https://www.moddable.com/documentation/base/base#timer

Steps to Reproduce
In the timers example, change the one shot length to an hour
// one shot (setTimeout)
const WAIT_TIME = 10006060;
Timer.set(() => trace("oneshot\n"), WAIT_TIME);

Run with mcconfig -d -m -p win

Expected behavior
The timer to be created

Images

[phoddie]

Thank you for your report.

This is a limitation of the underlying timer implementation provided by Windows, not the Timer module.

We've migrated the Timer module to use a more modern Windows API, TimerQueue. That should allow longer intervals. In addition, it should allow for more simultaneous timers. That change will appear in the next Moddable SDK release.

[amao-cbw]

Thank you for getting back so quick. Do you know what the limitations will be for the number of simultaneous timers and interval lengths in the next release?

[amao-cbw]

and is this only an issue when using the windows desktop simulator?

[phoddie]

Thank you for getting back so quick.

You are welcome.

Do you know what the limitations will be for the number of simultaneous timers and interval lengths in the next release?

They will be whatever limits Windows has on its TimerQueue API. I'm afraid I'm not an expert on that and, as I understand it, the limits may vary depending on the version of Windows you are using.

and is this only an issue when using the windows desktop simulator?

As noted above, the issue is in the "underlying timer implementation provided by Windows, not the Timer module."