"The latter should NEVER stop, as it is the number of milliseconds your system has been up"
I don't care about the number of milliseconds since my system has been up. I only care about the number of milliseconds my game has been running for. As the game should stop when you alt-tab out of it, so too should millisecs().
However, I can see how some people may desire that the game continue running when alt-tabbed out of. So that may not be the best solution.
I suppose a better solution would be for mark to create a special function which is called on return from an alt-tab event. That would allow us to put specialized code in there to handle the stuff ourselves. We can then create our own version of millisecs() which stops when our game stops and starts up again when it returns.
I don't care about the number of milliseconds since my system has been up. I only care about the number of milliseconds my game has been running for. As the game should stop when you alt-tab out of it, so too should millisecs().
However, I can see how some people may desire that the game continue running when alt-tabbed out of. So that may not be the best solution.
I suppose a better solution would be for mark to create a special function which is called on return from an alt-tab event. That would allow us to put specialized code in there to handle the stuff ourselves. We can then create our own version of millisecs() which stops when our game stops and starts up again when it returns.