gnu.gcj.xlib

Class Pixmap


public class Pixmap
extends Drawable

An X11 Pixmap. A pixmap is an offscreen drawable that resides on the X server. A pixmap is bound to the screen it was created for.

Field Summary

Fields inherited from class gnu.gcj.xlib.XID

display, xid

Constructor Summary

Pixmap(Drawable sameScreenAs, int width, int height, int depth)
Pixmap(XImage image, Screen screen)

Method Summary

protected static int
createXID(Drawable sameScreenAs, int width, int height, int depth)
protected void
finalize()
Called on an object by the Virtual Machine at most once, at some point after the Object is determined unreachable but before it is destroyed.

Methods inherited from class gnu.gcj.xlib.Drawable

copyIntoXImage, finalize, getBounds, getDepth

Methods inherited from class gnu.gcj.xlib.XID

getClientData, getDisplay, getXID, params, setClientData, toString

Methods inherited from class java.lang.Object

clone, equals, extends Object> getClass, finalize, hashCode, notify, notifyAll, toString, wait, wait, wait

Constructor Details

Pixmap

public Pixmap(Drawable sameScreenAs,
              int width,
              int height,
              int depth)

Pixmap

public Pixmap(XImage image,
              Screen screen)

Method Details

createXID

protected static int createXID(Drawable sameScreenAs,
                               int width,
                               int height,
                               int depth)

finalize

protected void finalize()
Called on an object by the Virtual Machine at most once, at some point after the Object is determined unreachable but before it is destroyed. You would think that this means it eventually is called on every Object, but this is not necessarily the case. If execution terminates abnormally, garbage collection does not always happen. Thus you cannot rely on this method to always work. For finer control over garbage collection, use references from the java.lang.ref package.

Virtual Machines are free to not call this method if they can determine that it does nothing important; for example, if your class extends Object and overrides finalize to do simply super.finalize().

finalize() will be called by a Thread that has no locks on any Objects, and may be called concurrently. There are no guarantees on the order in which multiple objects are finalized. This means that finalize() is usually unsuited for performing actions that must be thread-safe, and that your implementation must be use defensive programming if it is to always work.

If an Exception is thrown from finalize() during garbage collection, it will be patently ignored and the Object will still be destroyed.

It is allowed, although not typical, for user code to call finalize() directly. User invocation does not affect whether automatic invocation will occur. It is also permitted, although not recommended, for a finalize() method to "revive" an object by making it reachable from normal code again.

Unlike constructors, finalize() does not get called for an object's superclass unless the implementation specifically calls super.finalize().

The default implementation does nothing.

Overrides:
finalize in interface Drawable

Copyright (C) 2000 Free Software Foundation This file is part of libgcj. This software is copyrighted work licensed under the terms of the Libgcj License. Please consult the file "LIBGCJ_LICENSE" for details.