ArcGIS Engine Developer Guide

BUILDING APPLICATIONS WITH VISUAL JAVABEANS
public void addEventListeners() throws IOException {
pageLayout.addIPageLayoutControlEventsListener(
new IPageLayoutControlEventsAdapter() {
public void onPageLayoutReplaced(
IPageLayoutControlEventsOnPageLayoutReplacedEvent evt)
throws IOException{
map.loadMxFile(pageLayout.getDocumentFilename(), null, null);
map.setExtent(map.getFullExtent());
}
});
}
Buddying up the ToolbarBean and TOCBean
Although the components have been added to the JFrame, they do not yet ‘know
about each other’. For the controls to work in sync with each other, the TOC and
toolbar components should know the control with which they are associated.
Otherwise, the toolbar component will not know which component it is ‘controlling’,
and the TOC component will not know which component’s table of
contents it should display.
To set up this communication between the components, add the following code
to the buildAndShow() method after the load document code.
public void buildAndShow() throws IOException {
. . .
// Load a preauthored map document on the pageLayout component.
String documentPath = new java.io.File(
"../../data/gulf of st. lawrence.mxd").getAbsolutePath();
if (pageLayout.checkMxFile(documentPath))
pageLayout.loadMxFile(documentPath,null);
// Set buddy controls to wire up the TOC and Toolbar Beans
// with the PageLayout Bean.
toc.setBuddyControl(pageLayout);
toolbar.setBuddyControl(pageLayout);
} this.setVisible(true);
Adding commands to the toolbar
The toolbar control has been added to the user interface. By default, this control
is not populated with any tools. You will begin to add tools in the following
steps.
The ArcGIS Engine Developer Kit comes with more than 120 commands and
tools that work with the MapBean, the PageLayoutBean, and the ToolbarBean.
These commands and tools provide a lot of frequently used GIS functionality for
map navigation, graphics management, and feature selection. You will now add
some of these commands and tools to your application.
Chapter 6 • Developer scenarios • 311