Latest Contributions by Wolf

I was able to duplicate this issue.  It is a bug.  I also noticed that when you change this line in the constructor from this: SketchOutputMode = SketchOutputMode.Screen; to this: SketchOutputMode = SketchOutputMode.Map; This will limit your tool to Maps only it will not work on Scenes (3 D), however, the active tool doesn't switch to the Explore tool anymore. ... View more

Like Charles said we don't have enough code to see the problem, but i would also check your CrossHairControl and make sure that mapViewOverlayControl is defined.   ... View more

You are correct and it looks like you can add Topology items via the Pro UI | Add Data from Path: and here is the result (using the sample dataset from the community samples): However, when i try to perform the same operation through the API, the LayerFactory fails as you described: await QueuedTask.Run(() => { var path = @"C:\Data\Topology\GrandTeton.gdb\BackCountry\Backcountry_Topology"; Uri uri = new Uri(path); // fails: LayerFactory.Instance.CreateLayer(uri, MapView.Active.Map); }); I tried different methods and also tested this under 2.9 to no avail.  The only workaround i was able to find was adding the whole feature dataset instead of the Topology.  This works: await QueuedTask.Run(() => { var path = @"C:\Data\Topology\GrandTeton.gdb\BackCountry"; var uri = new Uri(path); LayerFactory.Instance.CreateLayer(uri, MapView.Active.Map); }); but needless to say, it will add all layers of that feature dataset to the map.  Consequently, all unwanted (or duplicated) layers have to be removed from the map's table of content. Thanks for finding this, i will report it as a bug. ... View more

Maybe i don't understand your workflow, but Topologies are applied to a feature dataset and not to a map.  In geodatabases, a topology is an arrangement that defines how point, line, and polygon features share coincident geometry. Topologies provide a mechanism to perform integrity checks on data and help validate and maintain better feature representations in a geodatabase.  To do this you have to use the GP Tool: Import Topology.  The tool requires two parameters: the feature dataset for which you want to create a topology and a topology definition file (XML - exported from a toplogy).  The tool creates a topology in the specified feature dataset, however, this only works if the feature dataset contains the feature classes listed in the topology_definition_file. Once you have a topology in your geodatabase you can use the topology functionality outlined in this ProConcept document:  ProConcepts Topology · Esri/arcgis-pro-sdk Wiki (github.com)   You can find code examples in these ProSnippets: ProSnippets Topology · Esri/arcgis-pro-sdk Wiki (github.com) ... View more

Charlie's suggestion is the way to go, however, you have to compute the x/y ratios to position the user control in the middle of the screen.  For that you have the use the active mapview's GetViewSize().   if (MapView.Active == null) return; var mapView = MapView.Active; var crossHairControl = new CrossHairControl(); // use the active mapview to get the size of the mapview display var xRatio = 0.0; var yRatio = 0.0; var viewSize = mapView.GetViewSize(); if (viewSize.Width != 0.0 && viewSize.Height != 0.0) { var xPosition = viewSize.Width / 2; var yPosition = viewSize.Height / 2; // now offset for 1/2 of the user control's size xPosition -= 16; yPosition -= 16; xRatio = xPosition / viewSize.Width; yRatio = yPosition / viewSize.Height; } // Create a MapViewOverlayControl using the user control var mapViewOverlayControl = new MapViewOverlayControl( crossHairControl, true, false, false, OverlayControlRelativePosition.Center, xRatio, yRatio); //Add to the active map view mapView.AddOverlayControl(mapViewOverlayControl); I attached my sample add-in, but the result should look like this:   ... View more

I guess i didn't understand your workflow correctly.  But in general, configurations allow you to modify the DAML when ArcGIS Pro starts up, but before the UI is activated.  This allows total control over the DAML content and hence the UI.  Add-ins are still loaded even if you run ArcGIS Pro with a Configuration, but you could modify the DAML of those Add-ins too (since the Add-in DAML will be included when Pro starts). Now states & conditions can be used to control the visibility of Tabs, Groups in an Add-in (no need for a Configuration to do this).   This ProGuide is talking about tabs and groups:  ProGuide Ribbon Tabs and Groups · ArcGIS/arcgis-pro-sdk Wiki (github.com) If you use a condition on an ArcGIS Pro button you can only disable the button, but you cannot hide it (or delete it) by using a condition.  But if you add your edit button (like the 'Delete' button) to an Edit group you can hide the whole group.  To test this out i modified the 'working with daml' sample code and hooked a new group 'myEdit_group' to the existing state/condition of the sample.  I can now use the 'Toggle State' button (which changes the condition) to hide or show the 'myEdit_group': after the toggle: This is the DAML that does the work:   <group id="myEdit_group" caption="My Edit Tools" keytip="X1" condition="example_state_condition"> <button refID="esri_core_saveProjectButton" /> <button refID="esri_core_saveProjectAsButton" /> </group>   and this adds the group to the mapping tab:   <updateModule refID="esri_mapping"> <tabs> <updateTab refID="esri_mapping_homeTab"> <insertGroup refID="myEdit_group"/> </updateTab> </tabs> ...     ... View more

Check the return value of edOp.Execute(); It might be false.  Also check if edOp.IsEmpty is set.  But yes I agree with Rich i don't see the need for a chained operation here either. ... View more

I couldn't find an easy way to do this.  We did reach out to the Dev team to see if we overlooked something here, but in the meantime the following snippet resets the extent to the extent before adding the new feature layer: QueuedTask.Run(() => { var map = MapView.Active.Map; var flyrCreateParam = new FeatureLayerCreationParams(new Uri(@"C:\Data\Admin\AdminData.gdb\USA\cities")) { Name = "World Cities", IsVisible = true }; var cameraBefore = MapView.Active.Camera; var featureLayer = LayerFactory.Instance.CreateLayer<FeatureLayer>( flyrCreateParam, map); if (cameraBefore != null) MapView.Active.ZoomTo(cameraBefore); }); Needless to say, this is just a work-around, once we hear back from the Dev team, I will let you know if there's a better way to accomplish your workflow. ... View more

I think you misunderstood, only the button images (*.png files usually located in the images/darkimages folders) need to be set to build action "AddinContent", not the class files (*.cs) those need to be compiled. ... View more

If you need a custom map tool that allows you to select a single annotation feature and then allows you to move it you can use the following code: internal class MoveAnnoTool : MapTool { public MoveAnnoTool() { IsSketchTool = true; SketchType = SketchGeometryType.Point; SketchOutputMode = SketchOutputMode.Map; } protected override Task OnToolActivateAsync(bool active) { return base.OnToolActivateAsync(active); } protected override Task<bool> OnSketchCompleteAsync(Geometry geometry) { { // execute on the MCT return QueuedTask.Run(() => { // find features under the sketch var features = MapView.Active.SelectFeatures(geometry); // only one feature ... if (features.Count != 1) return false; // this works only if one annotation feature has been // selected var annoSelected = 0; foreach (var annoLayer in features.ToDictionary().Keys.OfType<AnnotationLayer>()) { // are there features? var featOids = features[annoLayer]; annoSelected += featOids.Count; } if (annoSelected == 1) RunOnUiThread(() => { // or use ICommand.Execute ICommand cmd = FrameworkApplication.GetPlugInWrapper("esri_editing_EditVerticesMove") as ICommand; if ((cmd != null) && cmd.CanExecute(null)) cmd.Execute(null); }); return true; }); } } /// <summary> /// utility function to enable an action to run on the UI thread (if not already) /// </summary> /// <param name="action">the action to execute</param> /// <returns></returns> internal static void RunOnUiThread(Action action) { try { if (IsOnUiThread) action(); else System.Windows.Application.Current.Dispatcher.BeginInvoke(action); } catch (Exception ex) { MessageBox.Show($@"Error in OpenAndActivateMap: {ex.Message}"); } } /// <summary> /// Determines whether the calling thread is the thread associated with this /// System.Windows.Threading.Dispatcher, the UI thread. /// /// If called from a View model test it always returns true. /// </summary> public static bool IsOnUiThread => FrameworkApplication.TestMode || System.Windows.Application.Current.Dispatcher.CheckAccess(); } Click the tool and then click on an annotation feature, to select a feature, next the Pro Move command will be activated, and you can now move (rotate, scale) the annotation.   Once you moved a feature you can repeat.   You can insert additional custom code as needed. ... View more

Thanks Bill, I found similar issues before where introducing additional logging changed the timing and hence the execution sequence of threads that caused similar issues.   I will look over your code snippet and let you know if i see anything suspicious.  ... View more