IT. Expert System.

Android Reference


Class Shader

  • Direct Known Subclasses:
    BitmapShader, ComposeShader, LinearGradient, RadialGradient, SweepGradient

    public class Shader
    extends Object
    Shader is the based class for objects that return horizontal spans of colors during drawing. A subclass of Shader is installed in a Paint calling paint.setShader(shader). After that any object (other than a bitmap) that is drawn with that paint will get its color(s) from the shader.
    • Field Detail

      • native_instance

        public int native_instance
        This is set by subclasses, but don't make it public.
      • native_shader

        public int native_shader
    • Constructor Detail

      • Shader

        public Shader()
    • Method Detail

      • getLocalMatrix

        public boolean getLocalMatrix(Matrix localM)
        Return true if the shader has a non-identity local matrix.
        localM - If not null, it is set to the shader's local matrix.
        true if the shader has a non-identity local matrix
      • setLocalMatrix

        public void setLocalMatrix(Matrix localM)
        Set the shader's local matrix. Passing null will reset the shader's matrix to identity
        localM - The shader's new local matrix, or null to specify identity
      • finalize

        protected void finalize()
                         throws Throwable
        Description copied from class: Object
        Invoked when the garbage collector has detected that this instance is no longer reachable. The default implementation does nothing, but this method can be overridden to free resources.

        Note that objects that override finalize are significantly more expensive than objects that don't. Finalizers may be run a long time after the object is no longer reachable, depending on memory pressure, so it's a bad idea to rely on them for cleanup. Note also that finalizers are run on a single VM-wide finalizer thread, so doing blocking work in a finalizer is a bad idea. A finalizer is usually only necessary for a class that has a native peer and needs to call a native method to destroy that peer. Even then, it's better to provide an explicit close method (and implement Closeable), and insist that callers manually dispose of instances. This works well for something like files, but less well for something like a BigInteger where typical calling code would have to deal with lots of temporaries. Unfortunately, code that creates lots of temporaries is the worst kind of code from the point of view of the single finalizer thread.

        If you must use finalizers, consider at least providing your own ReferenceQueue and having your own thread process that queue.

        Unlike constructors, finalizers are not automatically chained. You are responsible for calling super.finalize() yourself.

        Uncaught exceptions thrown by finalizers are ignored and do not terminate the finalizer thread. See Effective Java Item 7, "Avoid finalizers" for more.

        finalize in class Object


Android Reference

Java basics

Java Enterprise Edition (EE)

Java Standard Edition (SE)





Java Script








Design patterns

RFC (standard status)

RFC (proposed standard status)

RFC (draft standard status)

RFC (informational status)

RFC (experimental status)

RFC (best current practice status)

RFC (historic status)

RFC (unknown status)

IT dictionary

All information of this service is derived from the free sources and is provided solely in the form of quotations. This service provides information and interfaces solely for the familiarization (not ownership) and under the "as is" condition.
Copyright 2016 © ELTASK.COM. All rights reserved.
Site is optimized for mobile devices.
Downloads: 4132 / 159436625. Delta: 0.00426 с