Hello developers - I have a stopwatch timer that is controlled by the application buttons (start/stop and split functions). At the POSE level, I am seeing anywhere between 30 to 110 milliseconds latency from the time I 'press' on a split button to the time when the application loop comes around to handle the hard3Chr case in my ButtonHandleEvent() function. Basically, this problem manifests itself in the accuracy of the time shown and when the button was actually pressed (down in the 10s of milliseconds, but that's still significant for my application). Without using a high speed camera and some other debugging aids on the actual handheld, I can't prove this phenomenom on the real device - only in the debugger environment of CW and POSE. I simply set a breakpoint in my ButtonHandleEvent() function when an app. button is pressed. I'm displaying the running time on the POSE screen and can look at what my software thinks it should be. The error is not cumulative for longer times, nor does it build up linearly as more splits are recorded (1st place versus 6th place). Has anyone seen this or have a more accurate way to handle time? Any thoughts? Regards John -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/tech/support/forums/
