I've done this in an application of mine, using QTimer polling every 5 - 10 seconds or so.
The only problem with the technique I find though is that if the tick happens 1 second before the start time, then it starts 4 seconds late.
Apart from actually shortening the interval, is there another way to get the schedule launched bang on time?

I understand that win32 has events you can hook into an event and wait using WaitForSingleObject which fires as soon as the clock ticks to the start time you're interested in. I'm not sure how crontab does it under *nix, but I've never seen a process start late before.
I'm feeling that it's going to be platform specific code here to get a reliable scheduler going. Am I wrong?


Steve