IT. Expert System.

Android Reference

DisplayEventReceiver


android.view

Class DisplayEventReceiver



  • public abstract class DisplayEventReceiver
    extends Object
    Provides a low-level mechanism for an application to receive display events such as vertical sync. The display event receive is NOT thread safe. Moreover, its methods must only be called on the Looper thread to which it is attached.
    • Method Summary

      Methods
      Modifier and Type Method and Description
      void dispose()
      Disposes the receiver.
      protected void finalize()
      Invoked when the garbage collector has detected that this instance is no longer reachable.
      void onHotplug(long timestampNanos, int builtInDisplayId, boolean connected)
      Called when a display hotplug event is received.
      void onVsync(long timestampNanos, int builtInDisplayId, int frame)
      Called when a vertical sync pulse is received.
      void scheduleVsync()
      Schedules a single vertical sync pulse to be delivered when the next display frame begins.
    • Constructor Detail

      • DisplayEventReceiver

        public DisplayEventReceiver(Looper looper)
        Creates a display event receiver.
        Parameters:
        looper - The looper to use when invoking callbacks.
    • Method Detail

      • 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.

        Overrides:
        finalize in class Object
        Throws:
        Throwable
      • dispose

        public void dispose()
        Disposes the receiver.
      • onVsync

        public void onVsync(long timestampNanos,
                   int builtInDisplayId,
                   int frame)
        Called when a vertical sync pulse is received. The recipient should render a frame and then call scheduleVsync() to schedule the next vertical sync pulse.
        Parameters:
        timestampNanos - The timestamp of the pulse, in the System.nanoTime() timebase.
        builtInDisplayId - The surface flinger built-in display id such as Surface.BUILT_IN_DISPLAY_ID_MAIN.
        frame - The frame number. Increases by one for each vertical sync interval.
      • onHotplug

        public void onHotplug(long timestampNanos,
                     int builtInDisplayId,
                     boolean connected)
        Called when a display hotplug event is received.
        Parameters:
        timestampNanos - The timestamp of the event, in the System.nanoTime() timebase.
        builtInDisplayId - The surface flinger built-in display id such as Surface.BUILT_IN_DISPLAY_ID_HDMI.
        connected - True if the display is connected, false if it disconnected.
      • scheduleVsync

        public void scheduleVsync()
        Schedules a single vertical sync pulse to be delivered when the next display frame begins.


Content

Android Reference

Java basics

Java Enterprise Edition (EE)

Java Standard Edition (SE)

SQL

HTML

PHP

CSS

Java Script

MYSQL

JQUERY

VBS

REGEX

C

C++

C#

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

License.
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: 339 / 159178158. Delta: 0.04545 с