I have multitasking ON in the DemoPad parameters. I discovered today, playing around with the real time clock feature of 1.4.3, that "multitasking" for DemoPad appears to mean 'keep the code loaded but don't give it any execution cycles'. My iDevice autolocked and when I unlocked it, the time displayed was stale even if I have a repeating page load that refreshes it every minute.
Reading further on IOS multitasking, I found that very few applications actually multitask, in the real sense of the word. This reminds me of the early days of IBM and this is sad
Is there any easy way within DemoPad to sense that the iDevice just came out of 'Lock' status, so I could immediately update the time instead of waiting for the "1 minute page load recurring action" ?
IOS multitasking
Re: IOS multitasking
You are correct, even with multi-tasking on, repeating page load actions do not execute. Why not just update the time every few seconds though?
Re: IOS multitasking
Just a mindset of minimizing processing. When DemoPad is running, a cycle of less than 1 minute would be wasteful. I guess I can live with a stale time for up to 60 seconds after a lock up.DemoPad wrote:You are correct, even with multi-tasking on, repeating page load actions do not execute. Why not just update the time every few seconds though?