IMapControlDefault Interface

Provides access to members that control the MapControl.

Product Availability

Available with ArcGIS Engine.

Description

The IMapControlDefault interface is the default dispatch interface that most development environments will automatically expose. For example, placing the MapControl in a container will typically generate an object called MapControl1. The properties and methods available directly on this object correspond to this interface, together with container specific properties and methods.

The IMapControlDefault interface is a 'pure' dispatch interface, so can be extended with new properties and methods at future releases of ArcGIS. The methods and properties are identical to the highest numbered main interface on the MapControl. For example, IMapControlDefault is equivalent to IMapControl4, but at future releases this could become IMapControl5. By using the IMapControlDefault interface you are guaranteed to always have access to the latest MapControl.

There is a small performance overhead in making calls through to a pure dispatch interface, but to avoid this you can QI to a specific interface. In some development environments it is not possible to QI directly on the control to other COM interfaces, because the control is contained within a wrapper object. Use the Object property to get the real control before performing the QI.

A property that specifies interception of key strokes that are normally handled by the container. When intercepted the OnKeyDown and OnKeyUp events will be called. This value can be a combined bit mask of esriKeyIntercept enum values.

CoClasses that implement IMapControlDefault

When querying interface to IMapControlDefault in Visual Basic .NET or Visual C# .NET the Object property or container specific code must be used. This is because .NET contains the real control inside a wrapper object known as an host.

When querying interface to IMapControlDefault in Visual Basic .NET or Visual C# .NET the Object property or container specific code must be used. This is because .NET contains the real control inside a wrapper object known as an host.