| Did you know ... | Search Documentation: |
| Instance variables |
Sometimes, it is desirable to allow the user to move the nodes of a
tree by hand. With tree<-auto_layout: @on
this is not possible as the tree will immediately move the node back to
the original position.
See also tree->compute
and tree->layout.
->eventtop-to-bottom.<-link
are used to determine the thickness, texture and colour of the lines.
Each node will, if it has sons, draw a line from (x + tree<-level_gap/2,
bottom side) down to halfway the last son. If to node is not the root,
it will draw a line from halfway its height towards the line from its
parent. See also node<->collapsed.
Note: the default tree is displayed left-to-right rather than top-to-bottom as the nodes are often much wider than high. Using left-to-right layout allows for displaying much larger hierarchies.
When a large number of items is to be displayed as an indented list,
also consider class list_browser.
The indentation may be realised using
list_browser->tab_stops.
->zoom
and tree->unzoom.
-root ->zoom->eventsend(Tree?link, arrows, first).
will attach an arrow pointing to the root to every relation created after this call has been made.
-link_gap -parent_handle -son_handle<-son_handle
and tree<-parent_handle.
-parent_handle -son_handle -link->level_gap ->neighbour_gap->event
This handle is automatically updated by tree->direction..
-link_gap -link ->direction -son_handle <-display_root.
Class tree delegates
messages not understood to its tree<-root
node when present.
If the argument is *nil, all nodes are removed from the tree. If the
argument is a new root object the behaviour depends on the relink
argument. With relink = @off
(default), the tree is first cleared using tree->root: @nil,
after which the new root is attached. With relink = @on
the old root is added as the only node->son
of the new root.
See also tree->zoom
and tree->unzoom.
-display_root->event<-parent_handle,
but is the connection-point for the connection towards son-nodes.
-link_gap -link -parent_handle