Passing a pointer as ID is very convenient. This way, the ID is always
It looks like you are still passing a pointer as the first parameter.
Don't do that.
And for timers with callback functions the first parameter is ignored. so
you can pass a 0.
The first parameter is generally a number INT (not a pointer to a number)
to be exact that the user (meaning you) choose as the id of the timer.
AliR.
"Nobody" <Nobody@yahoo.com> wrote in message
news:OJUg7bZfHHA.1312@TK2MSFTNGP03.phx.gbl...
If you call SetTimer with a callback, then OnTimer would not be called.
I was experimenting with callbacks and noticed that.
That is why I pointed it out.
I read your other post about the callback being in a seperate thread.
I suppose it would really have to be that way.
SetTimer((UINT)&callCounter,1000,
(TIMERPROC)CallCounterDisplayTimerProc);
SetTimer(MYID, 1000);
OnTimer() { MyFunc(); }
OnCallback(){ MyFunc(); }
The use of the first parameter with the callback function is also
useless.
I am unsure why it would be considered useless?
The Callback does get the nIDEvent.
I only used the Callback for 1 timer.
I stick to the OnTimer method besides.