C# Class Rhino.Tools.Debugger.Treetable.JTreeTable.TreeTableCellEditor

TreeTableCellEditor implementation.

TreeTableCellEditor implementation. Component returned is the JTree.

Inheritance: AbstractCellEditor, TableCellEditor

Show file Open project: hazzik/Rhino.Net

Public Methods

Method	Description
GetTableCellEditorComponent ( JTable table, object value, bool isSelected, int r, int c ) : Component
IsCellEditable ( Sharpen.EventObject e ) : bool	Overridden to return false, and if the event is a mouse event it is forwarded to the tree. The behavior for this is debatable, and should really be offered as a property. Overridden to return false, and if the event is a mouse event it is forwarded to the tree. The behavior for this is debatable, and should really be offered as a property. By returning false, all keyboard actions are implemented in terms of the table. By returning true, the tree would get a chance to do something with the keyboard events. For the most part this is ok. But for certain keys, such as left/right, the tree will expand/collapse where as the table focus should really move to a different column. Page up/down should also be implemented in terms of the table. By returning false this also has the added benefit that clicking outside of the bounds of the tree node, but still in the tree column will select the row, whereas if this returned true that wouldn't be the case. By returning false we are also enforcing the policy that the tree will never be editable (at least by a key sequence).

Private Methods

Method	Description
TreeTableCellEditor ( JTreeTable _enclosing ) : Java.Awt

Method Details

GetTableCellEditorComponent() public method

public GetTableCellEditorComponent ( JTable table, object value, bool isSelected, int r, int c ) : Component
table	JTable
value	object
isSelected	bool
r	int
c	int
return	Component

IsCellEditable() public method

Overridden to return false, and if the event is a mouse event it is forwarded to the tree.

The behavior for this is debatable, and should really be offered as a property.

Overridden to return false, and if the event is a mouse event it is forwarded to the tree.

The behavior for this is debatable, and should really be offered as a property. By returning false, all keyboard actions are implemented in terms of the table. By returning true, the tree would get a chance to do something with the keyboard events. For the most part this is ok. But for certain keys, such as left/right, the tree will expand/collapse where as the table focus should really move to a different column. Page up/down should also be implemented in terms of the table. By returning false this also has the added benefit that clicking outside of the bounds of the tree node, but still in the tree column will select the row, whereas if this returned true that wouldn't be the case.

By returning false we are also enforcing the policy that the tree will never be editable (at least by a key sequence).

public IsCellEditable ( Sharpen.EventObject e ) : bool
e	Sharpen.EventObject
return	bool