Choreographer Class

Definition

[Android.Runtime.Register("android/view/Choreographer", DoNotGenerateAcw=true)]
public sealed class Choreographer : Java.Lang.Object

[<Android.Runtime.Register("android/view/Choreographer", DoNotGenerateAcw=true)>]
type Choreographer = class
    inherit Object

Inheritance

Object

Object

Choreographer

Attributes

RegisterAttribute

Remarks

Coordinates the timing of animations, input and drawing.

The choreographer receives timing pulses (such as vertical synchronization) from the display subsystem then schedules work to occur as part of rendering the next display frame.

Applications typically interact with the choreographer indirectly using higher level abstractions in the animation framework or the view hierarchy. Here are some examples of things you can do using the higher-level APIs.

<ul> <li>To post an animation to be processed on a regular time basis synchronized with display frame rendering, use android.animation.ValueAnimator#start.</li> <li>To post a Runnable to be invoked once at the beginning of the next display frame, use View#postOnAnimation.</li> <li>To post a Runnable to be invoked once at the beginning of the next display frame after a delay, use View#postOnAnimationDelayed.</li> <li>To post a call to View#invalidate() to occur once at the beginning of the next display frame, use View#postInvalidateOnAnimation() or View#postInvalidateOnAnimation(int, int, int, int).</li> <li>To ensure that the contents of a View scroll smoothly and are drawn in sync with display frame rendering, do nothing. This already happens automatically. View#onDraw will be called at the appropriate time.</li> </ul>

However, there are a few cases where you might want to use the functions of the choreographer directly in your application. Here are some examples.

<ul> <li>If your application does its rendering in a different thread, possibly using GL, or does not use the animation framework or view hierarchy at all and you want to ensure that it is appropriately synchronized with the display, then use Choreographer#postFrameCallback.</li> <li>... and that's about it.</li> </ul>

Each Looper thread has its own choreographer. Other threads can post callbacks to run on the choreographer but they will run on the Looper to which the choreographer belongs.

Java documentation for android.view.Choreographer.

Portions of this page are modifications based on work created and shared by the Android Open Source Project and used according to terms described in the Creative Commons 2.5 Attribution License.

Properties

Methods

Explicit Interface Implementations

Extension Methods

Applies to