3
I believe you need to specify the two optional parameters to the Find method: documentBars.Find(cmdID, false, false);
From the Documentation:
noRecurse Use False to search all menus and toolbars for the item; otherwise use True. [Optional]
noCreate Use False if you want the item to get instantiated if it isn't already; otherwise use True. [Optional]
...
3
The correct solution turned out to be that Move shifts by a relative number of units. It is necessary to immediately transfer to the parameters by how much to shift (do not set relative to the center)
For example pTrans.Move(0, 0.2);
private void ExtendPolygon(ref IFeature pPolygonFt)
{
...
...
IPoint Center = ...
2
One of the benefits that VB.Net has over C# is its ability to use GeoProcessing Tools as objects with properties, not needing a VarArray to set the parameters. This is how I used them in my projects, with a function for each tool that I used. For example, this is the Add Join tool function:
Friend Function AddJoin(ByVal pInObject As Object, ByVal InFieldName ...
1
I ended up using WebClient.
// http://csharpexamples.com/download-files-synchronous-asynchronous-url-c/
using (WebClient webClient = new WebClient())
{
webClient.DownloadFile(remotePath, localPath);
}
1
Both IFeatureClass and IFeatureLayer are interfaces on the FeatureClass and FeatureLayer objects, respectively. These objects are very common to interacting with the features on the map and in the underlying data. I would suggest reviewing all the possible interfaces these objects implement here and here. This is the 10.3 documentation, but applies at least ...
1
Things like feature selection on the map and highlights happen at the layer level, not the feature class level. So while you can identify the features in the relationship class, you'll need to go to find the associated layers on your map and select the features through there. You can loop through the layers like this:
public IEnumerable<IFeatureLayer> ...
Only top voted, non community-wiki answers of a minimum length are eligible