This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
It's very usefull to have a table view (since OutlineView does not allow to hide the first column) But the interface and behavior of TableView should be similar as in other views. Eg.: - the TableView should have a setProperties method On the dev@openide.netbeans.org mailing list users reported problems, eg.: 1) Items from the table can't be dragged (yes, I did setDragSource(true) and called setAllowedDragActions) 2) On doubleclick, it doesnt open subnodes as ListView or TreeTableView does 3) When I have two views, i.e. ContextTreeView and TableView using the same ExplorerManager, the TableView doesn't react to the ContextTreeView's selection. ListView and others do. http://www.nabble.com/Problems-with-TableView---columns-in-OutlineView--td20672994.html
Sorry, wrong link: http://forums.netbeans.org/post-15454.html
Also the selection is somehow strange: - when selecting with the left mouse button, the selected cell does not have the foreground & background colors as the other cells of the selected row(s). - when selecting with the left mouse button, the selected cell does not provide a context menu as the other cells of the selected - when selecting with the right mouse button, context menu & coloring is correct, except if the cell, which was previously selected with the left mouse button is reselected. - strange coloring after the TableView regains the focus by selecting another cell of the selected row.
To the common explorer view interface belongs also a selectionMode property, I think.
The target milestone seems to be 6.8 What's the status?
Returning a custom editor from the Property for a given column isn't handler the same with the CellEditor for the table model. For example, returning a JButton instance in the PropertyEditor and painting it (when supportsPainting returns true), selecting the cell changes it back to a text cell and renders the toString() of the button. I had to do a big hack of using Proxy TableCellEditor and TableCellRenderers just to get this working.
Any one can provide a patch at least for some of these issues? If not, I don't feel able to implement them.