public class JXTreeTable.TreeTableHackerExt2 extends JXTreeTable.TreeTableHackerExt
Note: with 1.6 the expansion control was broken even with the "normal extended" TreeTableHackerExt. When fixing that (renderer must have correct width for BasicTreeUI since 1.6) took a look into why this didn't work and made it work. So, now this is bidi-compliant.
expansionChangedFlag| Constructor and Description |
|---|
TreeTableHackerExt2() |
| Modifier and Type | Method and Description |
|---|---|
protected boolean |
expandOrCollapseNode(int column,
EventObject e)
Tricksery to make the tree expand/collapse.
|
protected Point |
getTreeMousePoint(int column,
MouseEvent me)
This is a patch provided for Issue #980-swingx which should
improve the bidi-compliance.
|
isHitDetectionFromProcessMousecompleteEditing, expansionChanged, hitHandleDetectionFromEditCell, hitHandleDetectionFromProcessMouse, mightBeExpansionTriggerprotected boolean expandOrCollapseNode(int column,
EventObject e)
JXTreeTable.TreeTableHackerThis might be - indirectly - called from one of two places:
widened access for testing ...
expandOrCollapseNode in class JXTreeTable.TreeTableHackercolumn - the column index under the event, if any.e - the event which might trigger a expand/collapse.protected Point getTreeMousePoint(int column, MouseEvent me)
Problem was not in the translation to renderer coordinate system, it was in the method itself: the check whether we are "beyond" the cell content box is bidi-dependent. Plus (since 1.6), width of renderer must be > 0.
column - the column index under the event, if any.e - the event which might trigger a expand/collapse.Copyright © 2017. All Rights Reserved.