Example usage for android.view.animation Interpolator interface-usage

List of usage examples for android.view.animation Interpolator interface-usage

Introduction

In this page you can find the example usage for android.view.animation Interpolator interface-usage.

Usage

From source file com.anthonycr.progress.BezierEaseInterpolator.java

final class BezierEaseInterpolator implements Interpolator {

    private static final Interpolator sBezierInterpolator = PathInterpolatorCompat.create(0.25f, 0.1f, 0.25f, 1f);

    @Override
    public float getInterpolation(float input) {

From source file com.ofidy.ofidybrowser.ui.view.BezierEaseInterpolator.java

final class BezierEaseInterpolator implements Interpolator {

    private static final Interpolator sBezierInterpolator = PathInterpolatorCompat.create(0.25f, 0.1f, 0.25f, 1f);

    @Override
    public float getInterpolation(float input) {

From source file com.facebook.keyframes.util.KFPathInterpolator.java

/**
 * This class is directly lifted from the compat library's
 * {@link android.support.v4.view.animation.PathInterpolatorCompat}.  The reason we need this class
 * is to be able to control the precision ourselves for a smaller memory footprint.  The normal
 * PathInterpolator allocates ~1400 floats every time and holds on to this in memory for the entire
 * lifetime of the object, while this one allocates only 10% of that.  We dont need high precision

From source file com.actinarium.kinetic.util.LookupTableInterpolator.java

/**
 * <p>An interpolator that uses a lookup table to compute interpolation.</p><p><b>Note:</b> it is assumed that values
 * have fixed time step, so you must ensure it beforehand.</p><p>Derives from Apache 2.0 licensed code from Android
 * Support v4 Library, specifically {@link android.support.v4.view.animation.LookupTableInterpolator
 * LookupTableInterpolator}</p></p>
 *

From source file android.support.graphics.drawable.PathInterpolatorCompat.java

/**
 * An interpolator that can traverse a Path that extends from <code>Point</code>
 * <code>(0, 0)</code> to <code>(1, 1)</code>. The x coordinate along the <code>Path</code>
 * is the input value and the output is the y coordinate of the line at that point.
 * This means that the Path must conform to a function <code>y = f(x)</code>.
 *