Re: setTimer - what have I missed?
From: Platform Builder (markmo_at_qualnetics.com)
Date: 02/26/05
- Next message: Michael J. Salamone: "Re: ReadFileEx/WriteFileEx?"
- Previous message: Daniel Moth: "Re: GWES Exception !!??"
- In reply to: Bolla: "setTimer - what have I missed?"
- Messages sorted by: [ date ] [ thread ]
Date: 26 Feb 2005 10:16:29 -0800
In general, Windows SetTimer API should be avoided for any sort of
timing applicaton that requires any accuracy. The implementation of
WM_TIMER on Windows CE is handled by an application level priority
thread that may or may not get scheduled in a timeframe necessary to
send the WM_TIMER message. Recent versions of Windows CE allow that
thread priority to be change but still the publication of the WM_TIMER
message is dependent on the scheduling of a thread. Also the GWES
component that is necessary to support this timing mechanism is largely
single threaded due to the single critical section that gets taken when
entering most of the API's in GWES. This can delay the arrival or
processing of the timer message depending on what other applicatons are
doing with GWES. In general, WM_TIMER is not a good technology to use
if you need a reliable, accurate timing technology in Windows CE. It
is fine to use if there will be no fault in your system if the WM_TIMER
message arrives late or never arrives.
Mark Moeller
Chief Architect
Qualnetics Corporation
- Next message: Michael J. Salamone: "Re: ReadFileEx/WriteFileEx?"
- Previous message: Daniel Moth: "Re: GWES Exception !!??"
- In reply to: Bolla: "setTimer - what have I missed?"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
|
