-
Bug
-
Resolution: Fixed
-
P4
-
6
-
b07
-
generic
-
generic
-
Verified
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-2152910 | OpenJDK6 | Sergey Malenkov | P3 | Resolved | Fixed | b02 |
If we select several nodes using DefaultTreeSelectionModel.setSelectionPaths it's not quite clear which path in selection will be first. In other words what is the result of getSelectionPath() is undefined. It's not necessary first element of passed in TreePath array. It'll be useful to clarify this situation in the spec.
###@###.### 2004-12-17 12:17:44 GMT
This is closely connected with following JTree.getLastSelectedPathComponent problem.
By description:
Returns the last path component in the first node of the current selection.
getMinSelectionRow() returns the first selected row. But when we call getlastSelectedPathComponent it can return node, not corresponding to first selected row. See example in comments.
###@###.### 2004-12-17 14:02:37 GMT
###@###.### 2004-12-17 12:17:44 GMT
This is closely connected with following JTree.getLastSelectedPathComponent problem.
By description:
Returns the last path component in the first node of the current selection.
getMinSelectionRow() returns the first selected row. But when we call getlastSelectedPathComponent it can return node, not corresponding to first selected row. See example in comments.
###@###.### 2004-12-17 14:02:37 GMT
- backported by
-
JDK-2152910 Undefined behavior of DefaultTreeSelectionModel.getSelectionPath() after setSelectionPaths
-
- Resolved
-
- relates to
-
JDK-8040209 Ambiguous API document for JTree.setSelectionPaths
-
- Open
-
-
JDK-7080203 JTree.getSelectionPaths() now returns empty array instead of null
-
- Closed
-