Limitations of dynamic display


This document discusses restrictions when using dynamic display.

About limitations for dynamic display

There are a number of things to be aware of when using dynamic display. There are certain situations where it is not recommended to use dynamic display to obtain the best performance. In these situations, it is recommended to turn dynamic display off before proceeding. These situations include labeling, editing, using the graphic or ink tools, and printing.

Labels

Labels that are not annotated display a label in each tile. Therefore, many labels for one feature will be seen. Labels will be cut off on custom layers that don't return the correct extent.
Labels from MapServer layers will be slow when in Dynamic mode.

Editing

Edits will not show on the screen when dynamic display is enabled.
Graphic tools
When drawing graphics, the graphics and movements such as bring to front, nudges, and rotations will disappear until dynamic display is turned off. When dynamic display is enabled again, the graphic will appear. However, once it is displayed, selection handles around a selected graphic will not display.

Ink and tablet tools

Sketches made by ink or tablet tools disappear until dynamic display is turned off. Once dynamic display is enabled again, parts of sketches may be missing.

Data frame tools

Data frame tools such as the Viewer and Magnifier windows do not show dynamic content.

Effects tools

Effects tools such as Swipe and Flicker become disabled while dynamic display is enabled.

Publisher tools

A map can be published using the publishing tools but dynamic content will not show up in the published map.

Printing

Dynamic layers will not display in print preview, page layout, or paper output. Custom layers that contain dynamic items will print if the dynamic items are drawn in non-dynamic mode.

Symbols

The following restrictions on glyphs and polygons apply:
  • Glyphs cannot be polygons. Polygon symbols cannot contain different fill symbols. Therefore, polygon symbols are only supported through SimpleFillSymbol with solid fill.
  • In addition, drawing polygons with multiple rings, through the map or screen, is not supported. When drawing shapes, only simple polygons and polylines constructed from a list of points using the IPointsCollection interface are supported. For example, if a complex shape has only two points returned from its IPointCollection interface, then drawing a polyline using that shape will end up drawing one line between those two points.

Sharpness

Sharpness of some data sets may be lost when dynamic display is enabled. Once dynamic display is disabled, the original sharpness of the data will be restored.

Consolidated Layers

When using consolidated sub-layers, rendering may not be aligned with the minimum and maximum scale of the sub-layer, since the actual source scale that is being used for rendering the current scale, is snapped to a discrete predefined scale. Also, a consolidated sub-layer may not be aligned with the visibility state of the sub-layer in the TOC. When syncing the scale with the layer visibility is required, as an alternative you can un-consolidate the relevant sub-layers. Bear in mind that every non-consolidated layer that is added, consumes more memory and rendering resources.

Display

32 bit color depth display is a requirement for using dynamic display otherwise, you may see strange issues such as missing vector layers, weird colors and issues using dual monitors.
Content outside a circular map extent, such as when using myMapControl->put_VisibleRegion() which calls the Win32 API SetWindowRgn() doesn't function in an OpenGL window. The area outside the map extent will show up as black.