You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The shipped Sandcastle demo treats the "deactivation" case as Rectangle.MAX_VALUE, which is default.
Under-the-hood GlobeSurfaceTileProvider always checks tiles against the limiter rectangle but only modifies shaders for terrain tiles that intersect, so the default of Rectangle.MAX_VALUE shouldn't cause any shader modification.
I think it's the right level of abstraction to modify the setter in Globe.js so setting undefined percolates a Rectangle.MAX_VALUE down.
If you try setting
globe.cartographicLimitRectangle
toundefined
after it has previously been set, it will crash.Sandcastle
@likangning93 any ideas?
The text was updated successfully, but these errors were encountered: