Java JXtreeTable忽略树节点的getValueAt
我有一个JXTreeTable,它在左侧有一个节点树(不同的数据类型),在右侧有一个网格(默认情况下) 现在我希望所有显示的值(以及树标题)都取自getValueAt(row,column)方法,而不是树节点通过其toString()方法呈现 如何强制JXTreeTable不接受特定于类的toString()并使用getValueAt(…)返回的值 谢谢 这是我的模型:Java JXtreeTable忽略树节点的getValueAt,java,swing,swingx,treetable,Java,Swing,Swingx,Treetable,我有一个JXTreeTable,它在左侧有一个节点树(不同的数据类型),在右侧有一个网格(默认情况下) 现在我希望所有显示的值(以及树标题)都取自getValueAt(row,column)方法,而不是树节点通过其toString()方法呈现 如何强制JXTreeTable不接受特定于类的toString()并使用getValueAt(…)返回的值 谢谢 这是我的模型: public class TreeTableGroupTreeTableModel extends AbstractTreeT
public class TreeTableGroupTreeTableModel extends AbstractTreeTableModel {
private final static String[] COLUMN_NAMES = { "Tree",
"Add/Edit", "Remove" };
//Group-Hierarchy:
private JXGroup groupRootObject;
public TreeTableGroupTreeTableModel(JXGroup groupRoot) {
this.groupRootObject = groupRoot;
}
// Here is my structure:
//GROUP 1-1 ModuleAggregation 1-* Modules 1-1 JXGroupAccessMemberAggregation 1-* JXGroupAccessSimpleUserObjectLeaf
/**
* Returns the value for the node at columnIndex. The node must be managed
* by this model. Unamanaged nodes should throw an IllegalArgumentException.
*
*
* node - the node whose value is to be queried column - the column whose
* value is to be queried
*/
@Override
public Object getValueAt(Object node, int column) {
System.out.println(node.getClass());
if (node instanceof JXGroup) {
switch (column) {
case 0:
return "this should render this string instead of the class tostring()";//((JXGroup) node);
case 1:
case 2:
return "";
}
} else if (node instanceof JXGroupAccessModuleAggregation) {
switch (column) {
case 0:
return "Modules";
case 1:
return "ADD";
case 2:
return "REMOVE ALL";
}
} else if (node instanceof JXGroupAccessModule) {
switch (column) {
case 0:
return ((JXGroupAccessModule) node).getModule();
case 1:
return "ADD";
case 2:
return "REMOVE";
}
} else if (node instanceof JXGroupAccessMemberAggregation) {
switch (column) {
case 0:
return "Members";
case 1:
return "ADD";
case 2:
return "REMOVE ALL";
}
} else if (node instanceof JXGroupAccessSimpleUserObjectLeaf) {
switch (column) {
case 0:
SimpleUserObject c = FunctionsUser.getUser(
metaDataPackage.getUsers(),
((JXGroupAccessSimpleUserObjectLeaf) node).getUserId().getId());
return c.getShowAs();
case 1:
return "";
case 2:
return "REMOVE";
}
}
return null;
}
/**
* Sets the value for the node at columnIndex to value. The node must be
* managed by this model. Unamanaged nodes should throw an
* IllegalArgumentException.
*
* value - the new value node - the node whose value is to be changed column
* - the column whose value is to be changed
*/
@Override
public void setValueAt(Object value, Object node, int column) {
return; // changes are not allowed
}
@Override
public Object getRoot() {
return groupRootObject;
}
@Override
public int getColumnCount() {
return COLUMN_NAMES.length;
}
@Override
public String getColumnName(int column) {
return COLUMN_NAMES[column];
}
@Override
public boolean isCellEditable(Object node, int column) {
return false;
}
@Override
public boolean isLeaf(Object node) {
return node instanceof JXGroupAccessCategoryLeaf
|| node instanceof JXGroupAccessChapterLeaf
|| node instanceof JXGroupAccessEntryLeaf
|| node instanceof JXGroupAccessSimpleUserObjectLeaf;
}
@Override
public int getChildCount(Object obj) {
if (!(obj instanceof JXICountable)) {
System.out.println("parsing error. should be JXCountable (but is "
+ obj.getClass() + ")");
return 0;
}
JXICountable obj2 = (JXICountable) obj;
return obj2.getChildrenCount();
}
@Override
public Object getChild(Object parent, int index) {
if (parent instanceof JXITreeNodeAble) {
return ((JXITreeNodeAble) parent).getChild(index);
}
throw new IllegalArgumentException(
"parent is not a member of JXITreeNodeAble");
}
@Override
public int getIndexOfChild(Object parent, Object child) {
if (parent instanceof JXITreeNodeAble) {
return ((JXITreeNodeAble) parent).getIndexOfChild(child);
}
throw new IllegalArgumentException(
"parent is not a member of JXITreeNodeAble");
}
}
首先请注意,树表是最复杂的组件之一,因为节点必须保存大量数据:
- Hierarchical:给定父子关系
- 用户数据:通过
和setUserObject(..)
方法保存和检索特定于用户的对象getUserObject()
- 列数据:每个节点负责检索与每个列索引关联的数据,以便提供以表格形式表示的能力
TreeTableNodes
。有一个示例,作者修改了它的树表模型实现,以包含根节点。话虽如此,但至少有两件事需要修改:
getRoot()
方法,并保留从AbstractTreeTableModel
创建的实现super
构造函数public class TreeTableGroupTreeTableModel extends AbstractTreeTableModel {
...
// private JXGroup groupRootObject; Not needed!
...
public TreeTableGroupTreeTableModel(JXGroup groupRoot) {
super(groupRoot);
}
...
// @Override
// public Object getRoot() {
// return groupRootObject;
// }
...
}
虽然这可能会起作用(如果没有所有的类,我无法测试它),但我想再次强调,这种实现树表模型的方法对我来说并不合适。首先,我不会弄乱树表模型,而是使用DefaultTreeTableModel
。我还将为需要在树表中表示的每个域类实现一个树表节点。例如:
class JXGroupAccessModuleTreeTableNode extends AbstractMutableTreeTableNode {
public JXGroupAccessModuleTreeTableNode(JXGroupAccessModule module) {
super(module);
}
public JXGroupAccessModuleTreeTableNode(JXGroupAccessModule module, boolean allowsChildren) {
super(module, allowsChildren);
}
@Override
public Object getValueAt(int column) {
JXGroupAccessModule module = (JXGroupAccessModule)getUserObject();
switch (column) {
case 0: return module.getModule();
case 1: return "ADD";
case 2: return "REMOVE";
default: throw new ArrayIndexOutOfBoundsException(column);
}
}
@Override
public int getColumnCount() {
return 3;
}
}
要允许单元格可编辑,您必须同时覆盖setValueAt(Object value,int column)
和isEditable(column)
方法:默认情况下AbstractMutableTreeTableNodes
不可编辑
按照此方法,您将获得以下好处:
- 根本不需要弄乱树表模型
- 如果需要更改树结构,只需根据需要重新排列节点即可。再一次,没有必要修改任何模型的代码
- 每个节点的表示都与模型解耦,因此您可以用不同的方式表示相同的域对象,只需覆盖树表节点(而不是模型)中的两个方法即可
getValueAt(对象节点,int列)
?嗨,我遵循了这个示例(不使用UserObject或AbstractMutableTreeTableNodes):。这就是它从我的Employee类的normal toStrign()中获取值的原因吗?这是一种完全不同的使用方式JXTreeTable
,因为作者实现了自己的TreeTableModel
,以避免使用TreeTableNodes
。在这种情况下,如果不查看代码,我将无法帮助您。请考虑编辑您的问题,包括您的树表模型。有趣的帖子BTW@NikoHi,我添加了modelWow,这是很多代码。我想知道以这种方式实现TreeTableModel
的潜在瓶颈。现在我有了答案:调试/维护非常困难。See树表旨在使用TreeTableNodes
,并依赖这些节点通过getValueAt(int column)
方法提供列数据,如上所示。我最好的建议是:1)放弃自定义树表模型,使用设计用于树节点的DefaultTreeTableModel
。2) 根据需要定义多个树表节点,以保持分组层次结构@Nikoso你说只要扩展树型闪锌矿就能解决这个问题?问题是,我想将这些“JX对象”也用于其他树表(在getValueAt()中返回其他值)。所以我必须在模型的getValueAt()中进行主渲染,而不是在每个单独的节点对象中。。。