| java.lang.Object graphical.TreeViewGroup
TreeViewGroup | public class TreeViewGroup (Code) | | TreeViewGroup.
Open Issues
|
Field Summary | |
final public static int | ADDNODE | final public static int | CLEAR Force removal of all ListItems. | final public static int | CLEARCHANGE Clear change flag. | final public static int | DELETENODE | final public static int | UPDATEDETAIL Update details based on data in BinaryTree. | final public static int | UPDATENODE Update relevant ListItems based on data in BinaryTree. | final public static String | UPDATETHRUTVG Send performCommand( UPDATETHRUTVG, btn ) to targeted TreeViews. | final public static int | UPDATETITLE Update relevant ListItems based on passed title rather
than data in BinaryTree which is not necessarily updated
yet. |
ADDNODE | final public static int ADDNODE(Code) | | |
CLEAR | final public static int CLEAR(Code) | | Force removal of all ListItems.
|
CLEARCHANGE | final public static int CLEARCHANGE(Code) | | Clear change flag.
|
DELETENODE | final public static int DELETENODE(Code) | | |
UPDATEDETAIL | final public static int UPDATEDETAIL(Code) | | Update details based on data in BinaryTree.
See explanation under UPDATETHRUTVG.
|
UPDATENODE | final public static int UPDATENODE(Code) | | Update relevant ListItems based on data in BinaryTree.
|
UPDATETHRUTVG | final public static String UPDATETHRUTVG(Code) | | Send performCommand( UPDATETHRUTVG, btn ) to targeted TreeViews.
This is so TreeView subclasses that have details associated with
individual nodes can transmit data about changes to the details.
This is done as part of and UPDATENODE action and is the sole
purpose of and UPDATEDETAIL action.
|
UPDATETITLE | final public static int UPDATETITLE(Code) | | Update relevant ListItems based on passed title rather
than data in BinaryTree which is not necessarily updated
yet.
|
TreeViewGroup | public TreeViewGroup()(Code) | | |
sendAction | public void sendAction(TreeView treeView, int action, BTreeNode btn, String s)(Code) | | When performing certain actions, mimic those actions
in TreeViews showing the same data.
If the action to be performed is ADDNODE
the BTreeNode target is actually the parent of the
node to be affected.
Since drawing children depends on knowing the parent and
whether the parent is open or not and since in the
ADDNODE instance a new ListItem needs to be created
and therefore cannot be found, the parent is the target
for these actions.
DELETENODE targets the node itself because the BTreeNode
instance still exists, referenced in the local ListItem's
data() block (if there is a local ListItem).
It is also necessary to determine if the TreeView is rooted
at or below a deleted item, in which case the TreeView is
marked dead.
Otherwise, the parent is located and if displayed handled
the same way an ADDNODE is.
Both the update actions, UPDATENODE and UPDATETITLE target
the node itself.
UPDATENODE forces the node to be updated based on the data
in the corresponding BTreeNode.
This would be done typically when editing focus for that
node is lost in the originating TreeView.
UPDATETITLE is a special case which allows the title of
ListItems and the floating TextField to be modified without
reference to the BTreeNode.
It is necessary to do this because changing the key of the
BTreeNode is delayed to prevent sorting while the user is
typing.
Parameters: treeView - the treeView instance initiating the action Parameters: action - the action to be performed Parameters: btn - the BTreeNode the action affects Parameters: s - string used for UPDATETITLE |
|
|