Moview例子

------------------------------------------------------------------ Information Regarding the "MoView2" Sample MapObjects Map Viewer ------------------------------------------------------------------ Contents 1. What is MoView2? 2. How to use MoView2. 3. Troubleshooting. 1. What is MoView2? -------------------- MoView2 is an unsupported Visual Basic 6.0 sample application project. It has been designed to demonstrate much of the functionality provided with MapObjects version 2 within a simple application framework. You may use the Visual Basic code in MoView2 to jump-start your application development and for guidance on solving some practical interface issues when designing a graphical user interface for mapping. Some of MoView2 is documented in the book "Building Applications with MapObjects 2" which is provided with your MapObjects distribution. Additionally, you will find that the code within the modules of this project are commented quite liberally to help you follow the process flow. 2. How to use MoView2 ---------------------- Upon installation of the MapObjects software, the MoView sample application project is stored in this folder: <path_to_MapObjects>\samples\vb\MoView2 Inside this "MoView2" folder is a Visual Basic 6.0 project file called "MoView2.vbp". Startup Visual Basic and open this project with the "File | Open Project..." menu item. All of the modules (form, standard, class) that belong to this project will be present, all dependent controls will be listed in the toolbox, and all other referenced components will be available. *** IMPORTANT *** There is a small chance that you may receive error message popup windows generated by Visual Basic immediately upon attempting to open or run this project. This is an indicator of required components missing from your computer. MoView2 depends on several non-MapObjects components for proper operation. All of the components required to run MoView2 successfully are included either with the MapObjects software, or are included with Visual Basic. See the "Troubleshooting" section of this document for details on how to resolve any problems you may run into. 3. Troubleshooting ------------------- In order to use MoView2 error-free, you will need to ensure that the following controls have been installed onto your Visual Basic 6.0 development computer, and listed with the operating system registry along with their respective design-time licenses, if any. MO20.OCX - ESRI MapObjects 2 Map Control (version 2.x) GUID: 9BD6A640-CE75-11D1-AF04-204C4F4F5020 MO21LEGEND.OCX - MapObjects Helper Legend Control (version 2.01) GUID: C7FC2F7C-0688-11D5-B2F8-000102D87123 MSCOMCTL.OCX - Microsoft Windows Common Controls (version 6.0) GUID: 831FDD16-0C5C-11D2-A9FC-0000F8754DA1 MSFLXGRD32.OCX - Microsoft FlexGrid Control (version 6.0) GUID: 5E9E78A0-531B-11CF-91F6-C2863C385E30 COMDLG32.OCX - Microsoft Common Dialog Control (version 6.0) GUID: F9043C88-F6F2-101A-A3C9-08002B2F49FB TABCTL32.OCX - Microsoft Tabbed Dialog Control (version 6.0) GUID: BDC217C8-ED16-11CD-956C-0000C04E4C0A version 1.1#0 If you receive popup error message windows generated by Visual Basic during the opening of the "MoView2.vbp" project file, pay attention to the component name mentioned in the error, and use the information below to fix the problem regarding the missing component. The discussions below will help you trouble-shoot any control dependency problems you may have with the use of MoView2. MO20.OCX The first control listed above is the OCX file that is the major part of the MapObjects product you have installed onto your system. Your computer may have more than one copy stored onto it, however only one of these copies can be listed with your operating system's registry. Not only does the MO20.OCX need to registered, but this registered copy needs to be in the same folder as the MO20.LIC file. Registration of this control should have been done automatically when you originally installed the MapObjects software onto your computer, however there are a few extreme situations where your development copy of MO20.OCX can become unregistered. This possibility is true of any registered control. If this occurs, you will simply need to re-register this OCX. See the instructions below on how to register an OCX. This MO20.LIC file is needed to enable this use of the MO20.OCX in development mode. You do not need this MO20.LIC file to run applications that include MapObjects components, however you do need this file to build MapObjects applications or otherwise use the MO20.OCX in development-mode. It is against your license agreement with ESRI to distribute the MO20.LIC file to anyone else. MO21LEGEND.OCX This second control listed above is the map legend control used on MoView2's "frmMain" Form. It is a MapObjects Helper component that you can use to build legends into your MapObjects applications. This file is optionally installed with MapObjects 2.x, if the MapObjects Helper Components Option is selected during the installation process. This file simply needs to be listed with your operating system's registry in order to run applications that contain it, or for you to use this control in development-mode. It requires no additional license. If you find that you are unable to use this control in development-mode or at run-time, but the OCX file itself is in fact stored on your hard-drive (or otherwise accessible), then you will need to manually register the OCX with your operating system's registry. See the instructions below if this is necessary. If you find that you are unable to find this control anywhere accessible to your computer, you can install this file onto your computer by running MapObjects' SETUP.EXE again, selectively installing this legend component. MSCOMCTL.OCX GRID32.OCX COMDLG32.OCX TABCTL32.OCX The last four controls listed above are a part of the set of controls that are included as add-ons to your copy of Visual Basic 6.0. If they do not appear in your VB "Project | Components..." dialog box, try to find them installed on your PC anywhere. If you find them, load them into your operating system's registry using the instructions below. If you do not see them installed anywhere accessible to your computer, you will need to run Visual Basic 6.0 SETUP.EXE again to selectively install and register these components. Not only do these four controls need to be installed and registered onto your system, Microsoft requires that the design-time license for the use of these four controls be registered as well. To do this, merge the VBCTRLS.REG file in the \Tools\Controls folder of your VB product media into your registry. You can merge this file into your registry using REGSVR32.EXE (Win95 or WinNT4) or REGED32.EXE (WinNT3.51). The command syntax is: regedit vbctrls.reg Alternatively, on Windows 95 or Windows NT 4.0, you can right click on the VBCTRLS.REG file and select Merge on the context menu to merge licensing into your registry. INSTRUCTIONS ON HOW TO REGISTER OCX COMPONENTS There are three ways to register components (OCX, DLL, etc.) into your operating system's registry: 1) Run this command line: <path_to>REGSVR32.EXE <path_to_the_component_file> For example: C:\WINNT\SYSTEM32\REGSVR32.EXE C:\WHATEVER\MY.OCX 2) While in Explorer, right mouse click the OCX file and select "Register" from the pop-up menu. 3) While in Explorer, drag-drop the OCX file onto the REGSVR