As an unique ID, I always use an address of a variable that will keep it:
"Joseph M. Newcomer" <newcomer@flounder.com> wrote in message
Note that timer IDs are local to windows. So if you have a window with a
timer 1, any
other window is free to use a timer called 1 for its own purposes; if you
need two timers
in one window, they have to have different timer IDs. Unlike Win16, there
is no limit on
the number of timers, nor are they global IDs system-wide (or even
application-wide).
joe
On Thu, 05 Apr 2007 13:12:35 GMT, "jmarc" <jmarc@incursion-voyages.com>
wrote:
Whatever the number you want!
As long as you didn't use the same
number for another timer..
It can be the memory address of
the object who handle it. Every
object of a collection can have its
own timer..
Sometime, for a single timer, I
simply use "1234" as the ID..
jmarc...
"lucky" <Laxmanmaruthy@gmail.com> wrote in message
news:1175778140.570362.81110@l77g2000hsb.googlegroups.com...
Hi,
I have a dialog on which the timer is displayed using SetTimer() which
is binded to the dialog.Is there any API that identify this timer
which is got set .....
So that, with that id i can call some API which makes the timer to
start from that time it was already showing at.....
Joseph M. Newcomer [MVP]
email: newcomer@flounder.com
Web: http://www.flounder.com
MVP Tips: http://www.flounder.com/mvp_tips.htm