Custom Trees

Create a user-defined project navigation tree

Currently, all objects from the submenus Cross Sections, Variations and Structural Members of the menu “Geometry/Structure” are supported.

Create new trees by using the context menu (right mouse button).

In a tree, new tree items can be created.

You can assign particular existing objects to tree items (context menu Add/change link to object).

Tree items can also function as “nodes” or “structural levels” with subitems. In this case, it principally does not matter whether they have an object assigned to themselves or not (however, regarding this, see also management of drawing files below).

You can also directly add further objects as subitems to such existing tree nodes (context menu New Cross Section/Variation/Structural Member/Structural Connection) - they are thereby generated in the respective submenu of the menu “Geometry/Structure” and assigned to the created tree item. Note: You can also drag & drop objects from the menu Structure into the Tree.

Thus, in general, all tree items are only linked with the actual objects in the menu Structure. (Therefore, when deleting an item, you can only delete the tree item or also the referenced object). In the course of this, the same object can be referenced several times by different tree items.

Tree items and tree nodes can be moved within the tree structure per drag & drop.

Management of drawing files

The tree items created in the custom tree can be placed on certain drawing files when importing them to ALLPLAN.

For this, first, the option Use for ALLPLAN in the property window of the custom tree must be checked. Then, in the import dialog in ALLPLAN there is the possibility of selecting the respective custom tree (see Import ALLPLAN Civil data or rather Update ALLPLAN Civil data).

The assignment of the drawing file numbers for the particular tree items is always done in the Properties window of their proximately superordinate tree item without object assignment (=tree item functioning as mere tree node). In other words, a tree item that functions as a mere tree node contains the drawing file assignments of all proximately assigned tree items in its Properties window. If a tree item with object assignment, which thus functions as structural level at the same time, contains further tree items with object assignment as subitems, then all these receive the same drawing file assignment. Mere tree nodes having tree items with object assignment as their proximately superordinate structural level are themselves not transferred to ALLPLAN. The subitems of such a tree node receive their drawing file assignment from their next highest tree item with an assigned drawing file. See examples at the end of the page.

Further, only tree items with object assignments of the type structural member are considered for the export to ALLPLAN. All other tree items with different object assignments (cross sections, variations, static connections) are ignored. If a tree item with a not considered object assignment contains further subitems with (valid) object assignments of the type structural member, then these are not considered as well.

Moreover, an automatic numeration can be performed for a specific mere tree node for all of its inferior tree items (of all superordinate structural levels) via the context menu Enumerate drawing files. In doing so, the first drawing file number and a step width for all subsequent drawing files can be defined. It is possible to manually change the assignment of particular drawing files afterwards, however, using this function anew would overwrite these changes.

Export to Tcl-file

The objects linked to the tree items can be exported to a Tcl-file for each arbitrary tree item including its subordinate tree items. In this context it must be noted that only those objects are exported which are directly linked to the respective tree items of the exported tree structure. That means, for example, that a girder which references a cross section indeed keeps this reference, but the cross section itself is not exported, unless it is part of the exported tree structure. The objects of these exported (partial) Tcl-files can serve as templates for other projects and be added to other projects using the import option Add. The references to possibly missing objects (such as axes or cross sections) can be edited and adapted afterwards. For the top node of the custom tree itself there is an additional option Export tree items themselves when exporting to a Tcl-file, which also exports the tree structure of the custom tree itself.

Examples for structural levels with drawing file assignments

The drawing file assignment is always done at mere tree nodes for all proximately subordinate tree items with object assignment

Note: The numbers in brackets represent the structural levels.

Example 1:

(0) Custom tree

(1) Structure left (mere tree node): Drawing file assignment for DF1, DF2, DF3

(1.1) Box girder (tree item with object) -> DF1

(1.2) Pier 1 (tree item with object) -> DF2

(1.3) Pier 2 (tree item with object) -> DF3

Example 2:

(0) Custom tree

(1) Structure left (mere tree node): Drawing file assignment for DF1

(1.1) Box girder (tree item with object) -> DF1

(1.2) Piers (mere tree node): Drawing file assignment for DF2, DF3

(1.2.1) Pier 1 (tree item with object) -> DF2

(1.2.2) Pier 2 (tree item with object) -> DF3

Example 3:

(0) Custom tree

(1) Structure left (mere tree node): Drawing file assignment for DF1

(1.1) Box girder (tree item with object) -> DF1

(1.1.1) Pier 1 (tree item with object) -> TB1 (from box girder)

(1.1.2) Pier 2 (tree item with object) -> TB1 (from box girder)

Example 4:

(0) Custom tree

(1) Structure left (mere tree node): Drawing file assignment for DF1

(1.1) Box girder (tree item with object) -> DF1

(1.1.1) Pier 1 (tree item with object) -> TB1 (from box girder)

(1.1.2) Piles (mere tree node) (is not transferred to ALLPLAN, since superordinate tree node “(1.1) box girder” is not a mere tree node with drawing file assignment)

(1.1.2.1) Pile 1 (tree item with object) -> TB1 (from box girder)

(1.1.2.2) Pile 2 (tree item with object) -> TB1 (from box girder)