This document is archived and information here might be outdated. Recommended version. |
Esri PageLayoutControl
The PageLayoutControl encapsulates the PageLayout CoClass and provides additional properties, methods and events for: managing the general appearance, display properties and page properties of the control; adding and finding elements within the control; loading map documents into the control; dropping data onto the control from other applications; and printing.
Use the ISupportErrorInfo method InterfaceSupportsErrorInfo to determine if the object supports extended error information. If the object supports extended error info, VC++ developers should use the OLE/COM IErrorInfo interface to access the ErrorInfo object. Visual Basic developers should use the global error object Err to retrieve this extended error information.
Interfaces | Description |
---|---|
IConnectionPointContainer (esriDisplay) | |
IMxdContents (esriCarto) | Provides access to members to pass data into and out off a MXD map document file. Coclasses that implement this interface can limited the implementation to one property if required. |
IPageLayoutControl | Provides access to members that control the PageLayoutControl. |
IPageLayoutControl2 | Provides access to members that control the PageLayoutControl. |
IPageLayoutControl3 | Provides access to members that control the PageLayoutControl. |
IPageLayoutControlDefault | Provides access to members that control the PageLayoutControl. |
IPageLayoutControlEvents | Provides access to events that occur with user interaction to the PageLayoutControl. |
IPersist (esriSystem) | |
IPersistStreamInit (esriGeoDatabase) | |
ISupportErrorInfo (esriSystem) | |
ITOCBuddy | Provides access to members that control the TOC buddy. |
ITOCBuddyEvents | Provides access to events that notify the TOC of a change. |
IToolbarBuddy | Provides access to members that control the ToolbarControl buddy. |
The PageLayoutControl uses a ScreenDisplay as the display object for drawing and will therefore react to the same keyboard and mouse actions as the ScreenDisplay object.
There is no need to declare the PageLayoutControl 's outbound interface as described below in most development environments, because the interface is automaticlly implemented.