33
33
all node-types are expanded/collapsed, i.e. the two options above
34
34
takes no effect for these files.
36
<h5>Automatic expanding the ECB-methods-buffer</h5>
36
<h5>Automatic expansion ot tags after buffer-parsing</h5>
38
<p>With the option <code>ecb-show-tags</code> you tell ECB how to display tags
39
of a certain tag-class (see <a href="Customizing-the-display.html#Customizing%20the%20display">Customizing the display</a>). Among other
40
things you can tell ECB that a certain tag-class should be combined
41
under an expanded or collapsed bucket-node. But such a setting defines
42
the expansion-state of such a bucket-node only direct afterwards the
43
buffer has been (re)parsed, which can occur after opening a file,
44
after autom. reparsing the buffer via semantic or after manually
45
rebuilding the methods-buffer of ECB.
47
<p>The tag-class <code>type</code> (classes, interfaces, enumerations etc.) is
48
divided into several subtypes by semantic. The subtypes are stings
49
which names exactly if the tag with tag-class <code>type</code> is a class,
50
an interface, an enumeration, a typedef etc. With the option
51
<code>ecb-type-tag-expansion</code> you can tell ECB if these type-tags
52
should be autom. expanded after (reparsing) a buffer (see above) or if
53
they should be displayed collapsed - so all its members (methods,
54
variables etc.) are hidden.
56
<h5>Automatic expanding the ECB-methods-buffer for current tag</h5>
38
58
<p>If the option <code>ecb-highlight-tag-with-point</code> is switched on, then
39
then always that node in the method-buffer is highlighted which
40
belongs to the current semantic-tag under point in the current active
59
always that node in the method-buffer is highlighted which belongs to
60
the current semantic-tag under point in the current active
41
61
edit-window. But if this node is invisible (probably because its
42
62
parent node is collapsed) then no node is highlighted if the auto.
43
63
expanding feature is switched off.
54
74
<p>The autom. expanding feature is only available for semantic-sources!
76
<p>Previous versions of ECB have always fully expanded the whole tree in
77
the Methods-buffer if the current tag in the source-buffer was not
78
visible in the current tree - e.g. because the variables-bucket was
79
collapsed or the containing type of a tag (e.g. the class of a method)
80
was collapsed. So in most cases much more was expanded as needed to
81
make the current tag visible.
83
<p>The mechanism of ECB 2.22 and higher only expands the needed parts of
84
the tree-buffer to make the related node visible: First we try to
85
highlight the current tag with current expansion-state of the
86
Methods-buffer. If the node is not visible so the tag can not be
87
highlighted then we go upstairs the ladder of type-tags the current
88
tag belongs to (e.g. we expand successive the nodes of the whole
89
class-hierachy of the current method-tag until the related node
90
becomes visible). If there is no containing type for the current tag
91
then the node of the tag is probably contained in a toplevel-bucket
92
which is currently collapsed; in this case we expand only this
93
bucket-node and try highlighting again. Only if this has still no
94
success then we expand the full tree-buffer and try to highlight the
97
<p>There is another option
98
<code>ecb-auto-expand-tag-tree-collapse-other</code>: If this option is set
99
then auto. expanding the tag-tree collapses all not related nodes.
100
This means that all nodes which have no relevance for the currently
101
highlighted node will be collapsed, because they are not necessary to
102
make the highlighted node visible. This feature is switched off by
103
default because if always collapses the complete Methods-tree before
104
the following highlighting of the node for the current tag expands the
105
needed parts of the tree-buffer.
added
removed
html-help/Expanding.html
