foo

Sun公司官方网站上下载的JDK文档

the specified data flavor is available.
<br>
<li><a href="../../../api/java/awt/datatransfer/Clipboard.html#getData(java.awt.datatransfer.DataFlavor)">Object getData(DataFlavor)</a> returns the
data in the specified data flavor.
</ul>
</blockquote>

<h3><a
href="http://developer.java.sun.com/developer/bugParade/bugs/4790833.html">
      <b>4790833</b></a>:
Memory Usage No Longer Shoots Up using Clipboard.getContents</h3>
<blockquote>
Prior to this release, <code>Clipboard.getContents</code> fetched
clipboard data in all provided formats for which a mapping to the
corresponding data flavor in the default flavor map exists.
If there were a lot of formats and the data were large, a lot
of memory was consumed with the fetched data in different formats.
Thanks to the new methods introduced with bug fix
<a 
href="http://developer.java.sun.com/developer/bugParade/bugs/4287795.html">
4287795</a>, this problem has been fixed.
</blockquote>

<h3><a
href="http://developer.java.sun.com/developer/bugParade/bugs/4415175.html">
      <b>4415175</b></a>:
New API to Globally Change the DnD Gesture Motion Threshold</h3>
<blockquote>
The drag motion gesture threshold represents the number of pixels
the cursor is dragged before the data transfer system initiates
a drag operation.  Prior to this release, this was hard-coded to 5
pixels.  As of release 1.5, there is support for picking up the
desktop properties for drag sensitivity and mapping it to the
threshold, and new API that allows users to get and change this
threshold.  The new API includes:
<ul>
<li><a href="../../../api/java/awt/dnd/DragSource.html#getDragThreshold()">java.awt.dnd.DragSource.getDragThreshold()</a>
<li>java.awt.dnd.drag.threshold</a> (a property)
<li><a href="../../../api/java/awt/dnd/MouseDragGestureRecognizer.html">java.awt.dnd.MouseDragGestureRecognizer</a> (updated class spec)
</ul>
</blockquote>

<h3><a
href="http://developer.java.sun.com/developer/bugParade/bugs/4712068.html">
      <b>4712068</b></a>:
DnD Usability Issue for Dragging Text</h3>
<blockquote>
Prior to this release, the hotspot of the drop icons used on
X platforms was
located at the middle of the icon.  When dragging text, the
text cursor moves to indicate the current drop location, but
this was obscurbed by the drop icon itself.  For this release,
the drop cursors used on X platforms have been changed to 
point to the upper-left corner of the drop icon. 
The corresponding hotspots have been changed accordingly.
</blockquote>

<h3><a
href="http://developer.java.sun.com/developer/bugParade/bugs/4191708.html">
      <b>4191708</b></a>:
Clarification in spec for several java.awt.dnd.DropTarget methods</h3>
<blockquote>
The doc has been clarified with respect to passing in a null
parameter for the following <code>java.awt.dnd.DropTarget</code> methods:
<ul>
<li><a href="../../../api/java/awt/dnd/DropTarget.html#dragEnter(java.awt.dnd.DropTargetDragEvent)">dragEnter(DropTargetDragEvent)</a>
<br>
<li><a href="../../../api/java/awt/dnd/DropTarget.html#dragOver(java.awt.dnd.DropTargetDragEvent)">dragOver(DropTargetDragEvent)</a>
<br>
<li><a href="../../../api/java/awt/dnd/DropTarget.html#dropActionChanged(java.awt.dnd.DropTargetDragEvent)">dropActionChanged(DropTargetDragEvent)</a>
<br>
<li><a href="../../../api/java/awt/dnd/DropTarget.html#drop(java.awt.dnd.DropTargetDragEvent)">drop(DropTargetDragEvent)</a>
<br>
<li><a href="../../../api/java/awt/dnd/DropTarget.html#dragExit(java.awt.dnd.DropTargetDragEvent)">dragExit(DropTargetDragEvent)</a>
</ul>
</blockquote>

<h3><a
href="http://developer.java.sun.com/developer/bugParade/bugs/4819437.html">
      <b>4819437</b></a>:
DragSourceListener.dragExit is now called in a consistent way</h3>
<blockquote>
<!-- Previously, <code>DragSourceListener.dragExit(DragSourceEvent)</code>
was called whenever the current drop site rejected the drag. 
If the drop site rejected the drag
as soon as the drag entered the drop site,
<code>DragSourceListener.dragExit</code> was
called and no other <code>DragSourceListener</code> method was called. 
For this release, the behavior was changed to call <code>dragExit</code>. -->
The class specification for the
<a href="../../../api/java/awt/dnd/DragSourceAdapter.html">DragSourceAdapter</a> and
<a href="../../../api/java/awt/dnd/DragSourceAdapter.html">DragSourceAdapter</a>
classes, and the documentation for the 
<a href="../../../api/java/awt/dnd/DragSourceAdapter.html#dragExit()">DragSourceAdapter.dragExit</a> and
<a href="../../../api/java/awt/dnd/DragSourceListener.html#dragExit()">DragSourceListener.dragExit</a>
methods have been updated to clarify the notion that the drop site is
associated with the previous call to <code>dragEnter</code>.
</blockquote>

<h3><a
href="http://developer.java.sun.com/developer/bugParade/bugs/4654688.html">
      <b>4654688</b></a>:
SystemFlavorMap Methods Now Consistent with Documentation</h3>
<blockquote>
The <code>SystemFlavorMap</code> class is
used to store mappings between native formats and Java data
flavors in order to support data transfer between native and
Java applications.  The documentation for the
<a href="../../../api/java/awt/datatransfer/SystemFlavorMap.html#getNativesForFlavor(java.awt.datatransfer.DataFlavor)">SystemFlavorMap.getNativesForFlavor(DataFlavor)</a>
method has been clarified to say that a <code>DataFlavor</code>
(or a native format) is known if and only if it has at least one
static mapping associated with it.
</blockquote>

<h3><a
href="http://developer.java.sun.com/developer/bugParade/bugs/4123385.html">
      <b>4123385</b></a>:
Clarification of Behavior for DragSourceDragEvent and DragSourceDropEvent
Constructors</h3>
<blockquote>
Previously, several constructors in the
<code>java.awt.dnd.DragSourceDragEvent</code> and
<code>java.awt.dnd.DragSourceDropEvent</code>
classes were throwing unspecified <code>IllegalArgumentException</code>s.
In general, these constructors didn't describe the behavior for null arguments.
For this release, the specification for the following constructors 
has been clarified to explain the behavior for null arguments
and to document the <code>IllegalArgumentException</code> that may occur.
<ul>
<li><a href="../../../api/java/awt/dnd/DragSourceDragEvent.html#DragSourceDragEvent(java.awt.dnd.DragSourceContext, int, int, int)">DragSourceDragEvent(DragSourceContext, int int, int)</a>
<li><a href="../../../api/java/awt/dnd/DragSourceDragEvent.html#DragSourceDragEvent(java.awt.dnd.DragSourceContext, int, int, int, int, int)">DragSourceDragEvent(DragSourceContext, int int, int, int, int)</a>
<li><a href="../../../api/java/awt/dnd/DragSourceDropEvent.html#DragSourceDropEvent(java.awt.dnd.DragSourceContext)">DragSourceDropEvent(DragSourceContext)</a>
<li><a href="../../../api/java/awt/dnd/DragSourceDropEvent.html#DragSourceDropEvent(java.awt.dnd.DragSourceContext, int, boolean)">DragSourceDropEvent(DragSourceContext, int, boolean)</a>
<li><a href="../../../api/java/awt/dnd/DragSourceDropEvent.html#DragSourceDropEvent(java.awt.dnd.DragSourceContext, int, boolean, int, int)">DragSourceDropEvent(DragSourceContext, int, boolean, int, int)</a>
</ul>
</blockquote>

</blockquote>
<a name=layout><h2>Layout Bugfixes</h2></a>
<blockquote>

<h3>GridBagLayout Bugfixes</h3>
<blockquote>
<b>GridBagLayout</b>: Several bugfixes have been implemented for
GridBagLayout.  Note that two of these bugs listed apply to the
documentation only.  The most significant bugfixes include:
<h3><a
href="http://developer.java.sun.com/developer/bugParade/bugs/4254022.html">
      <b>4254022</b></a>:
More than 512 horizontal or vertical components are now possible in a
GridBagLayout</h3>
<blockquote>
Previously, GridBagLayout had been implemented with a hard-coded
width and height limit of 512.  This is now allocated dynamically and
the MAXGRIDSIZE constant is no longer used.
</blockquote>

<h3><a
href="http://developer.java.sun.com/developer/bugParade/bugs/4532201.html">
      <b>4532201</b></a>:
GridBagLayout.lookupConstraints doc is clarified</h3>
<blockquote>
Documentation was added to clarify what happens when the specified
Component is not in the grid bag layout.
</blockquote>

<h3><a
href="http://developer.java.sun.com/developer/bugParade/bugs/4618355.html">
      <b>4618355</b></a>:
Doc for GridBagLayout.gridwidth/gridheight is clarified</h3>
<blockquote>
The class spec for GridBagLayout.gridwidth/gridheight was
confusing in its description of REMAINDER and RELATIVE.  This
has been corrected.
</blockquote>
</blockquote>

<h3>FlowLayout Bugfixes</h3>
<blockquote>
<b>FlowLayout</b>: Several documentation bugs have been fixed for
FlowLayout
<h3><a
href="http://developer.java.sun.com/developer/bugParade/bugs/4586806.html">
      <b>4586806</b></a>:
FlowLayout spec is corrected regarding alignment</h3>
<blockquote>
Previously, the class spec stated that components are centered
on the line.  Actually, the <code>align</code> property determines
how the components are laid out.  The doc has been corrected.
</blockquote>

<h3><a
href="http://developer.java.sun.com/developer/bugParade/bugs/4881919.html">
      <b>4881919</b></a>:
FlowLayout class spec no longer implies that components are always
left to right</h3>
<blockquote>
The FlowLayout class spec was written before the ability
to go right to left was added.  Therefore it assumed that left to
right was the only possible orientation.  The doc has been corrected.
</blockquote>

<h3><a
href="http://developer.java.sun.com/developer/bugParade/bugs/4587456.html">
      <b>4587456</b></a>:
Corrected spec for FlowLayout constructor</h3>
<blockquote>
Previously, the doc for the FlowLayout constructor neglected to
mention that the hgap and vap were applied to the spacing between the
components and the container border as well as between the components.
The documentation has been corrected.
</blockquote>
</blockquote>

<h3><a
href="http://developer.java.sun.com/developer/bugParade/bugs/4172932.html">
      <b>4172932</b></a>:
New methods to get constraints for children in BorderLayout</h3>
<blockquote>
Three public methods have been added to <code>BorderLayout</code>,
one to get the constraints for a component, and two different ways
to get the component for a given constraint (one takes component
orientation into account and the other doesn't).  The new methods
are:
<ul>
<li><a href="../../../api/java/awt/BorderLayout.html#getLayoutComponent(java.lang.Object)">Component getLayoutComponent(Object)</a>
<br>
<li><a href="../../../api/java/awt/BorderLayout.html#getLayoutComponent(java.awt.Container,java.lang.Object)">Component getLayoutComponent(Container, Object)</a>
<br>
<li><a href="../../../api/java/awt/BorderLayout.html#getConstraints(Component)">Object getConstraints(Component)</a>
</ul>
</blockquote>

<h3><a
href="http://developer.java.sun.com/developer/bugParade/bugs/4515041.html">
      <b>4515041</b></a>:
Clarified spec for GridLayout.layoutContainer regarding vgap and hgap params</h3>
<blockquote>
Previously, the spec for layoutContainer stated that the vgap and hgap
was added between each cell and between the first/last cell and the border.
In reality, the gaps are applied between the components only.  This has
been corrected in the doc.
</blockquote>

</blockquote>
<a name=misc><h2>Miscellaneous Bugfixes</h2></a>
<blockquote>

<h3><a
href="http://developer.java.sun.com/developer/bugParade/bugs/4533021.html">
      <b>4533021</b></a>:
New API to Change the Z-ordering of Children</h3>
<blockquote>
New API has been added to specify the z-ordering of children
in a <code>Container</code>. The two new <code>Container</code>
methods include:
<ul>
<li><a href="../../../api/java/awt/Container.html#getComponentZOrder(java.awt.Component, int)">getComponentZOrder(Component, int)</a>
<li><a href="../../../api/java/awt/Container.html#setComponentZOrder(java.awt.Component, int)">setComponentZOrder(Component, int)</a>
</ul>
</blockquote>