The picture to the left is an example of a construct hierarchy diagram.  To display this diagram, choose Information.Show Constructs from the menu.  The menu item is only available for data file views and compiled I.F. views.

The tree control looks very much like the node browser, except it is static--nothing about the tree can be manipulated.  This is because the tree is a rendition of the construct relationships per their organization in an I.F.  The actual tree of a data file might look very different; the construct hierarchy diagram is designed to show what could be rather than what is.

In a construct hierarchy diagram, you can view two construct types that are not available in the node browser:  node lists and decision lists.  All children of node lists in this tree describe a natural order for organized block children (which may or may not be repeated).  All children of decision lists in this tree describe the possible choices for any one construct at a particular point in deserialization.

A construct hierarchy diagram does not fully do justice to deserialization and serialization nuances associated with a binary file format.  The actual implementations of the I.F. critical steps, including routines such as Validation, BlockSize, and Termination, are not described in the diagram.  The menu item Information.Show File Info or simply looking at an implementation file's source code can help to understand the finer elements of deserialization and serialization.

  See also: [Viewing node information] [Viewing the log] [Viewing memory blocks]
[Viewing file information] [Determining I.F. protocol support] [Load/Save failure reporting]