Re: WM_TIMER remaining/elapsed time...
You could simulate a pause by just keeping track of the timer tick downs
(seconds) in your own variable and decrement it every time the timer is
called. Then to pause, you would essentially stop the timer, but keep the
variable (a member of your class). Then to start you would use the amount
of time not ticked off (using the variable) to set the timer again.
When the timer finishes you could you stop and start it again using the full
amount of time again as part of the timer handler.
You could also have a flag, like your busy flag, that just ignores the
timer firing when it happens and returns immediately without doing anything.
This would simulate doing a pause (at least in the functionality of it).
Tom
"Simon" <bad@example.com> wrote in message
news:eUH0kcG6KHA.4508@TK2MSFTNGP06.phx.gbl...
On 2010/04/30 02:48 PM, Tom Serface wrote:
Hi Simon,
Did you get an answer that works for you? I want to make sure your
problem got solved.
Hi,
Thanks for the reply, in the end I just added a flag that does something
like.
// -----------------------------
OnTimer( ... )
{
if( busy )
{
timer_is_complete = true;
}
else
{
DoSomething();
}
}
...
DoingSomStuff()
{
// do the stuff
if( true == timer_is_comlete )
{
DoSomething();
}
}
// --------------------------------
But I am not 100% happy with it. I would prefer to pause the timer. That
way, when you resume the timer the normal chain of events will happen.
I could write my own timer class using a thread but this would add a lot
over testing overhead to the current app.
I will almost certainly create a branch with a bunch of tests before going
live with it.
Thanks again
Simon