Correct me if I’m wrong, but timer triggers do not fire when the device is not active? In the scenario where users “re-activate” their devices, how do timer triggers respond? Does the timer trigger start counting from 0, where it previously ended, or calculate the total elapsed time since the device become inactive?
Main use case for me right now is to update records as employees re-open their devices.
We use iPads to use check sheet applications. Very much like its paper counterpart, the check sheet is not accessed continuously and is often only referenced for a few seconds at a time (to fill in a few check items or to reference the current check being worked on). I want to use a timer trigger to save work time in intervals of 1 minute or whenever their device becomes active again, which will update the aggregation that shows total time of process.
Will setting a timer trigger work for this scenario? Or will the timer trigger never fire unless the user stays on that step for the allotted interval before de-activating their device?
As long as the computer is awake and the player is actively running, then timers should continue to fire. The moment player is closed or the computer goes to sleep, then timers would stop (as would the rest of the application).
For example, if you close the Tulip player and re-open it, the timer will reset.
Example: 60 second timer, close player app at 30 seconds and re-open, will wait another 60 seconds for it to fire
Instead if the computer goes to sleep, it pauses the timer instead. So when the computer wakes up, it will resume as if no time has passed.
Example: 60 second timer, computer sleeps at 30 seconds, 30 minutes later, you wake the computer up, timer will fire in 30 seconds.
Might be a stupid question but I wanted to check what happens when someone changes applications on an iPad? Does the timer restart because the player was not officially closed? Or does Tulip Player treat an application switch as closing the app?
On iOS and iPadOS the app is “suspended” when it goes to the background, so it should have the same behavior as Jake stated above!
As a side note, on Android, the app will continue to run in the background until the Android OS decides to kill or suspend the app at some non-deterministic time. This could be from memory or cpu pressure, aging or other android version or OEM specific heuristic.
