|
POST
|
You should be able to QI from IMapDocument to IDocumentVersion, set the version property and save.
... View more
09-21-2012
05:18 AM
|
0
|
0
|
931
|
|
POST
|
I don't think there's any way to listen for the actual event. One solution would be to put a timer on your dockable window that would fire every second or so and get the selected item from the TOC contents view.
... View more
09-18-2012
07:13 AM
|
0
|
0
|
776
|
|
POST
|
You're using a geoprocessing tool. The geoprocessing environment has a global setting to automatically add outputs to the map. You can turn it off, either through the ArcMap UI or through code (IGeoProcessor.AddOutputsToMap).
... View more
09-18-2012
07:08 AM
|
0
|
0
|
897
|
|
POST
|
I'm not sure if it will help anyone else who comes a long this thread, but the problem was that I was trying to my code in a stand alone code inside of Visual Studio. I had to convert my code into a button to get around the error. So, it's definitely an issue with the library references. If your application is standalone then you need to be checking out a license prior to running any code that uses ArcObjects. If you're using ArcGIS 10 or higher you will also need to bind to a product.
... View more
09-18-2012
05:05 AM
|
1
|
2
|
3896
|
|
POST
|
I have a form with a button on it. The button's click event activates a tool which in turn gets the a point object. My question is how can the form get the point from the tool so that the x and y values can be used in the form? Robert One solution is to write a generic tool that allows the user to click the map (or draw a rectangle, a line, a circle, a polygon or whatever). The tool would then fire an event and pass in the geometry as one of the arguments. The code behind your form would include an event handler for this event that does whatever you need to do with that point geometry (for example, select a feature on a certain layer and populate controls with its attributes). The code behind the button would create a new instance of your tool, subscribe to its event and activate the tool.
... View more
09-10-2012
06:59 AM
|
0
|
0
|
2217
|
|
POST
|
Make sure your project(s) is referencing the ArcGIS 10 ESRI assemblies and no longer referencing the ArcGIS 9.2 ESRI assemblies.
... View more
09-10-2012
06:47 AM
|
0
|
0
|
1187
|
|
POST
|
The IWorkspaceFactory and IWorkspaceFactory2 interfaces are included in the esriGeodatabase library. The ShapefileWorkspaceFactory class is included in the esriDataSourcesFile library. The developer help will tell you which library an interface or class belongs to. There is also a Library Locator tool that installs to the ArcGIS\Developer Tools program group on your Start menu.
... View more
09-05-2012
10:21 AM
|
0
|
0
|
830
|
|
POST
|
You haven't set pFeatureClass to anything. You have to set it to something before you can use it.
... View more
09-05-2012
05:03 AM
|
0
|
0
|
436
|
|
POST
|
You can't put a tool on a menu. You can only put commands on menus. A workaround is to create a command that activates the tool and put that command on the menu.
... View more
08-30-2012
05:39 AM
|
0
|
0
|
737
|
|
POST
|
Before removing the layer from the map you should disconnect it from its data source by calling IDataLayer2.Disconnect.
... View more
08-23-2012
05:59 AM
|
0
|
0
|
1534
|
|
POST
|
Make sure your target platform is set to the 3.5 .NET Framework. VS2010 defaults to the 4.0 .NET Framework when you create new projects, which is not supported by the ESRI SDK at ArcGIS 10.
... View more
08-23-2012
05:06 AM
|
0
|
0
|
1671
|
|
POST
|
You're using aMapDocument to create the mxd then using pMapDocument to open that mxd and make changes to it. When you try to save using pMapDocument, you're getting the lock error because aMapDocument still has the file open. Use one or the other, but not both.
... View more
08-22-2012
12:22 PM
|
0
|
0
|
1165
|
|
POST
|
For each path you create a new instance of the Polyline class then add the path to it's geometry collection.
... View more
08-22-2012
12:15 PM
|
0
|
1
|
1020
|
|
POST
|
I forget which is which, but one is the old geoprocessor class and is still provided for compatibility with previous versions. The one you should be using for new code is the one in which you create an instance of the geoprocessing tool you want to use, set the parameters by accessing properties on that class and then pass the instance of that class into the geoprocessor's Execute method. The old way requires you to fill a property set with the parameters then pass the name of the geoprocessing tool as a string into the Execute method along with the property set.
... View more
08-20-2012
12:41 PM
|
0
|
0
|
1177
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 06-20-2014 05:29 AM | |
| 1 | 02-01-2011 04:18 AM | |
| 1 | 02-04-2011 04:15 AM | |
| 1 | 01-17-2014 03:57 AM | |
| 1 | 10-07-2010 07:37 AM |
| Online Status |
Offline
|
| Date Last Visited |
11-11-2020
02:23 AM
|