public static final class JTree.DropLocation extends TransferHandler.DropLocation
TransferHandler.DropLocationrepresenting a drop location for a
|Modifier and Type||Method||Description|
Returns the index where the dropped data should be inserted with respect to the path returned by
Returns the path where dropped data should be placed in the tree.
Returns a string representation of this drop location.
clone, equals, finalize, getClass, hashCode, notify, notifyAll, wait, wait, wait
public int getChildIndex()
For drop modes
DropMode.ON, this index is unimportant (and it will
-1) as the only interesting data is the
path over which the drop operation occurred.
For drop mode
DropMode.INSERT, this index
indicates the index at which the data should be inserted into
the parent path represented by
-1 indicates that the drop occurred over the
parent itself, and in most cases should be treated as inserting
into either the beginning or the end of the parent's list of
DropMode.ON_OR_INSERT, this value will be
an insert index, as described above, or
the drop occurred over the path itself.
public TreePath getPath()
Interpretation of this value depends on the drop mode set on the
component. If the drop mode is
DropMode.ON, the return value is the path in the
tree over which the data has been (or will be) dropped.
null indicates that the drop is over empty space,
not associated with a particular path.
If the drop mode is
DropMode.INSERT, the return value
refers to the path that should become the parent of the new data,
in which case
getChildIndex() indicates where the
new item should be inserted into this parent path. A
null path indicates that no parent path has been
determined, which can happen for multiple reasons:
If the drop mode is
getChildIndex can be used to determine whether the
drop is on top of the path itself (
-1) or the index
at which it should be inserted into the path (values other than
public String toString()
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, 2017, Oracle and/or its affiliates. 500 Oracle Parkway
Redwood Shores, CA 94065 USA. All rights reserved.