Timing control for script-based animations
Timing control is used mainly in animations for cyclic script execution synchronized with screen changes.
Making script-based animations requires updating the properties of the animated objects in each frame. In computerized animations, the frame rate is normally 30 or 60 fps (frames per second), because the human eye perceives a sequence of images as an animation when they change at least 12-15 times per second. The requestAnimationFrame() (or webkitRequestAnimationFrame()) method of the WindowAnimationTiming interface enables scheduling the animation frame update requests. The frame update rate depends on implementation. In Tizen SDK version 2.2, it is about 60 fps.
| Note |
|---|
In mobile applications, when using the Emulator, you must include the webkit prefix in method names, such as window.performance.webkitNow(). However, when using a device, the prefix must not be used. In addition, when using the Emulator, methods assigned to variables must be formatted as follows:
window.performance.windowNow = window.performance.now || window.performance.webkitNow || Date.now; window.performance.windowNow(); In wearable applications, when you are using the Emulator and want to support backward compatibility, methods assigned to variables must be formatted as follows: window.performance.windowNow = window.performance.now || window.performance.webkitNow || Date.now; window.performance.windowNow(); |
