About Dependent Views

You can create multiple copies of a view that are dependent on the primary view.

All copies, known as dependent views, remain synchronous with the primary view and all other dependent views, so that when view-specific changes (such as view scale and annotations) are made in one view, they are reflected in all views.

Creating dependent views may be useful in the following scenarios:

Dependent views display in the Project Browser under the primary view. You can insert matchlines to indicate where the view is split, and view references to link views.

Example

The following image shows a project view that has been split into 2 dependent views. The primary view is shown in the drawing area with its crop region and the crop regions for the dependent views visible, a matchline indicating where the view is split (dashed blue line), and view references (1/A102 and 1/A101).

Supported View Types for Dependent Views

You can create dependent views for plan views, elevation views, section views, and callout views. When you create dependent section, elevation, or callout views, a new section, elevation, or callout symbol is generated on top of the original symbol. You can move the new symbol independently.

Visibility and Graphic Settings for Dependent Views

When you add view-specific information to a primary view or a dependent view, it is visible in all related views. You can specify visibility and graphic overrides to individual elements on a per-view basis. This allows you to clean up areas where there is overlap between related views. For more information, see About Hiding Elements in a View.

Dependent Views and View Properties

A dependent view inherits view properties and view-specific elements from the primary view. Synchrony is kept between the primary view and dependent views for the following view properties:

The following properties can vary between the primary view and dependent views: