Grid Bubble Location Relative to the Scope Box

[jra.140737]

How do I control exactly how the grid bubbles are associated to the scope box. Currently if I associate a grid to the scope box the bubble is located exterior to the scope box. I want exact control where I can have it offset a certain distance inside the scope box. Is there a way to do this?

-Joe

[Steve_Stafford]

There is no user controlled/accessible variable for the offset applied when the grids are associated with a scope box. If I recall it is "set" to 1" offset from the scope box boundary when printed.

The scope box "owns" the 3D model extents of the grid(s). Any change to the position is considered a 2D view specific override which you have complete control over, except that you now have to manage that. You can use Propagate Extents (Options Bar when grids are selected) to mitigate the drudgery of the task though.

[Christopher_L]

There is no user controlled/accessible variable for the offset applied when the grids are associated with a scope box. If I recall it is "set" to 1" offset from the scope box boundary when printed.

The scope box "owns" the 3D model extents of the grid(s). Any change to the position is considered a 2D view specific override which you have complete control over, except that you now have to manage that. You can use Propagate Extents (Options Bar when grids are selected) to mitigate the drudgery of the task though.

I realize this post is ancient but I'm strugling with exactly the same problem: Views controlled by scope boxes and grids that stick out to far. I have tried to propogate extents but without success. I get no "propagate extents dialog" as the help file says I should.
What am I missing?

[cliff collins]

Try either:

Select all Grids, disassociate with Scope Box.
Select all Grids, associate with scope box.

Delete Scope Box.
Create new scope box, associate grids.

[Steve_Stafford]

Sorry I was a bit cavalier when I wrote about propagate extents back then. If a view has its crop region turned on then Revit doesn't consider it eligible for propagate extents. It isn't able to determine how to interpret different crop boundary extents to apply such a change. As soon a the crop region is activate propagate extents ceases working based in that view, nor can it be applied or extend to other datum in other views that have their crop region on.