Expand and Fold Instance

The Expand and Fold instance feature allows you to traverse up (Fold Instance) and down (Expand Instance) the design hierarchy of a SmartDesign component.

An instance of a SmartDesign component, which contains lower level hierarchies that can be expanded or folded in place. Expanded means traversing one level of hierarchy for viewing. Fold means the design is collapsed to the next higher level. The expand or fold instance is a read-only view of the component.

The Expand and Fold actions are executed in place. The result of the Expand and Fold Instance appears in the same location, relative to the rest of the design in the same window. No new window is opened.

A folded design is indicated by a + sign at the top-left corner of the design. Clicking the + sign expands the folded design to the next lower levels of hierarchy. Alternatively, right-click the instance and select Expand Inplace.

Figure 1. Top-Level Design - Folded

???

An expanded design is indicated by a - sign at the top-left corner of the design. Clicking the - sign collapses the design hierarchy to the next higher level of hierarchy. Alternatively, right-click the instance and select Fold Instance.

Figure 2. Top-Level Design - Expanded

???

When a lower level of the design hierarchy is modified, the parent block that instantiates the modified lower level is indicated by the asterisk (*) next to the name in the SmartDesign Component Name tab to indicate a change. If the modified block is two levels of hierarchy down, the design blocks of the next two higher levels have the asterisk (*) next to their names (in the SmartDesign tab) to indicate that the design component has changed. The modified block is highlighted in red and have status icon on the top-right side of the block.

Note: The red highlight and the warning icon appear only after the higher level block(s) is folded and expanded again to expose the changed lower level block.
Figure 3. Red Highlight and Changed_Module Identification

???
Note: Instead of ports changed, the error becomes missing module if any one of the following conditions occurs:

If the changed or missing module/block is at the lowest level of hierarchy, the Update Instance and Generate Components steps must be repeated at every level of hierarchy above the changed module or block until the top-level hierarchy is reached, updated, and regenerated.