public class Popup extends Object
Component
to the user, typically
on top of all the other Component
s in a particular containment
hierarchy. Popup
s have a very small life cycle. Once you
have obtained a Popup
, and hidden it (invoked the
hide
method), you should no longer
invoke any methods on it. This allows the PopupFactory
to cache
Popup
s for later use.
The general contract is that if you need to change the size of the
Component
, or location of the Popup
, you should
obtain a new Popup
.
Popup
does not descend from Component
, rather
implementations of Popup
are responsible for creating
and maintaining their own Component
s to render the
requested Component
to the user.
You typically do not explicitly create an instance of Popup
,
instead obtain one from a PopupFactory
.
PopupFactory
protected Popup(Component owner, Component contents, int x, int y)
Popup
for the Component owner
containing the Component contents
. owner
is used to determine which Window
the new
Popup
will parent the Component
the
Popup
creates to.
A null owner
implies there is no valid parent.
x
and
y
specify the preferred initial location to place
the Popup
at. Based on screen size, or other paramaters,
the Popup
may not display at x
and
y
.owner
- Component mouse coordinates are relative to, may be nullcontents
- Contents of the Popupx
- Initial x screen coordinatey
- Initial y screen coordinateIllegalArgumentException
- if contents is nullprotected Popup()
Popup
. This is provided for subclasses.public void show()
Popup
visible. If the Popup
is
currently visible, this has no effect.public void hide()
Popup
. Once a Popup
has been disposed you should no longer invoke methods on it. A
dispose
d Popup
may be reclaimed and later used
based on the PopupFactory
. As such, if you invoke methods
on a disposed
Popup
, indeterminate
behavior will result. Submit a bug or feature
For further API reference and developer documentation, see Java SE Documentation. That documentation contains more detailed, developer-targeted descriptions, with conceptual overviews, definitions of terms, workarounds, and working code examples.
Copyright © 1993, 2015, Oracle and/or its affiliates. All rights reserved.