deleting views deletes details along

In continuation to yesterday's blog,

If a view is deleted, Revit gives a warned like this sometimes:

Revit basically lists all the callout views that were created in this deleted view. For eg. when you create a callout view in a view called 'xyz', Revit assigns the view 'xyz' as the callout view's parent. And when the parent view gets deleted, the callout view is also get deleted.

If you dont want this to happen, you can change the Parent View parameter to none in the callout view's property.

Changing this value automatically changes the Far clip settings to 'independent' and the 'Show in' parameter to 'intersecting views'

Now deleting the parent view will not delete these callouts.

(just to irritate you, now, if you changed the value of the 'show in' parameter to "none" then the callout tag wont be visible in any views...!)

That brings us back to the best practices: It is always good to create callouts from the Primary view or in just one dedicated view, which you might never have to delete.

Dependent Views and callout tags

I wrote sometime back about dependent views.

Here is another quirk.

It was my understanding that all the annotation objects are synced among all the dependent views and its Primary view. (This rule does not apply to "Element Hide".) The idea was that you could add annotation in any view, and as long as the annotation crop does not crop it, the annotation will be visible in other views.

When we create a new callout view from one of the dependent views, the callout tag is not visible in other dependent views and in the primary view. That's a bummer.

However, if you change the value of the "Show In" parameter in the view property to "Intersecting views" from "Parent View only" like

then the callout tag shows up in other views.

Ironically, this works only for the callout view type 'Detail'. If the callout view type is 'Floor Plan', this 'show in' parameter is not available. You cannot convert a Floor Plan view type to a Detail type too.

Any other view type created, like elevation, sections, etc. are visible in all relevant views. They don't have this affliction.

Also, if you create any view type (including callouts) in the Primary view, those will be visible in all relevant views. Looks like the best practice is to create any necessary view in the primary view only.