Re: DispatchMessage: What is message # 0xC0FE ?
- From: "Alexander Grigoriev" <alegr@xxxxxxxxxxxxx>
- Date: Mon, 25 Dec 2006 09:32:06 -0800
As long as you're not trying to measure intervals over 47 days, or don't
compare two of those values, you're OK. tick count difference is safe to use
and compare. Tick count absolute value is NOT safe to compare.
"Joseph M. Newcomer" <newcomer@xxxxxxxxxxxx> wrote in message
news:92guo2p4248jp1mpsslqt5midqn98t7qvt@xxxxxxxxxx
*supposed* to take 2 seconds? Or you are using something like
GetTickCount, which doesn't
measure the time taken to execute the dispatch. And isn't very reliable
for other than
approximate-clock-time, if you don't mind the fact that every few days it
tells you it
took a couple days because of 32-bit rollover.
joe
.
- References:
- DispatchMessage: What is message # 0xC0FE ?
- From: Susan Rice
- Re: DispatchMessage: What is message # 0xC0FE ?
- From: Joseph M . Newcomer
- DispatchMessage: What is message # 0xC0FE ?
- Prev by Date: global mouse hook but, it stops!!
- Next by Date: Re: deletion of System::String
- Previous by thread: Re: DispatchMessage: What is message # 0xC0FE ?
- Next by thread: hardware detection
- Index(es):
Relevant Pages
|