Identifies the faces of people in a
Bitmap graphic object.
|FaceDetector.Face||A Face contains all the information identifying the location of a face in a bitmap.|
Creates a FaceDetector, configured with the size of the images to be analysed and the maximum number of faces that can be detected.
Finds all the faces found in a given
Invoked when the garbage collector has detected that this instance is no longer reachable.
Creates a FaceDetector, configured with the size of the images to be analysed and the maximum number of faces that can be detected. These parameters cannot be changed once the object is constructed. Note that the width of the image must be even.
|width||the width of the image|
|height||the height of the image|
|maxFaces||the maximum number of faces to identify|
|faces||an array in which to place all found
|IllegalArgumentException||if the Bitmap dimensions don't match the dimensions defined at initialization or the given array is not sized equal to the maxFaces value defined at initialization|
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
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
Uncaught exceptions thrown by finalizers are ignored and do not terminate the finalizer thread. See Effective Java Item 7, "Avoid finalizers" for more.