Potential 6 ms latency of the timer -~ 6 ms latency in the timer

If you have developed Windows Mobile gestureGesturephysicsengine. hThe header file is defined as follows:

/// <Summary>
/// Defines a common value for a normal Frame delay rate expected to be used when displaying
/// Output from the physics engine. we are aiming at 25fps and also allow ~ 6 ms latency in the timer
/// </Summary>
# Define Gesture_animation_frame_delay_ms34 

 

The file is in the.. \ Windows Mobile 6 SDK \ pocketpc \ include \ armv4i \"Directory. The approximate meaning of the comment is:

"Defines a public value for the normal frame latency rate, which is used when the physical engine displays the output. The target is 25 FPS and the potential 6 ms latency in the timer is allowed ."

 

From the above note, we can know that there may be 6 seconds of delay after each frame is refreshed, And the set latency is 34 Ms, so the actual time required for each frame is 40 ms.

The above definition also illustrates this:

# Define Gesture_animation_frame_delay_ms34 

1000/34 ≈ 29;

If the latency is 6 ms:

1000/(34 + 6) = 25;

This is exactly the same as 25 FPS in the comment, which proves our point of view.