Latest Contributions by NarelleChedzey

Hi, Can you change the definition of your OnSelectionChange function to the following and see if that helps with the method firing when a choice is made in the combobox.    Protected Overrides Sub OnSelectionChange(layerName As ComboBoxItem) (so it is Overrides not Overridable Overloads)   Narelle     ... View more

Hi,  I'm sorry;  I'm not able to duplicate your problem with FeatureLayerCreationParams.  I have a group layer containing 3 layers (pointing to a file geodatabase).  Then I run the following code which inserts a hosted feature layer at index 2 in the group layer.   The new layer is inserted at the correct location.  Can you run this code and see if it works as you expect?     Narelle protected override void OnClick() { var groupLayer = MapView.Active.Map.GetLayersAsFlattenedList().OfType<GroupLayer>().FirstOrDefault(); if (groupLayer == null) return; // Airports_OPSNET45 string agolId = "8c1854a8580543b0a4848a0b5fbb0791"; int index = 2; DoIt(agolId, "My layer", index, groupLayer); } internal Task DoIt(string AgolId, string name, int index, GroupLayer groupLayer) { return QueuedTask.Run(() => { Item stagingLayer = ItemFactory.Instance.Create(AgolId, ItemFactory.ItemType.PortalItem); if (LayerFactory.Instance.CanCreateLayerFrom(stagingLayer)) { var featureCreateParams = new FeatureLayerCreationParams(stagingLayer) { IsVisible = true, MapMemberIndex = index, MapMemberPosition = MapMemberPosition.Index, Name = name }; Lactory.Instance.CreateLayer<FeatureLayer>(featureCreateParams, groupLayer); } }); }       ... View more

Hi,    You seem to be missing setting the MapMemberPosition to MapMemberPosition.Index in the first code snippet (when you are using the FeatureLayerCreationParams).    The default value for this property when it is not set is AutoArrange which means that the MapMemberIndex value is ignored.    Thanks Narelle   ... View more

Hi,    Seeing you're reading just a .txt file - I would recommend using standard .NET read/write classes/methods to open your file rather than the FileSystemConnectionPath object.  https://learn.microsoft.com/en-us/dotnet/visual-basic/developing-apps/programming/drives-directories-files/how-to-read-text-from-files-with-a-streamreader This link has a code snippet which seems to suit your situation -  opening a text file and reading lines.    Thanks Narelle ... View more

Hello,    Currently there is no method in the API to access the set of favorite templates.  Access to templates is currently only from a map member (layer or standalone table) using the GetTemplates method.  I will add an issue to our backlog to address this in a future release.    Narelle ... View more

Hi Mody,  This is by design.  We do not receive a modified event for point geometry from the underlying architecture.   Unfortunately there is no other event available for points.    Narelle   ... View more

Hi Tom,    Please see the information I posted here.  https://community.esri.com/t5/arcgis-pro-sdk-questions/integration-and-configuration-of-custom-commands/m-p/1206677#M8659   let me know if there are additional questions.    Narelle ... View more

Dirk,     You will likely have to restructure some of your code to fully implement the ability of embedding your dockpane into the Tasks pane.    The daml category that you found ("esri_tasks_embeddableControls") is the correct category to register your code in order for Tasks to recognize it as a component that can be embedded.  But the view/viewModel that the daml entry references via the className attribute should be a class that inherits from ArcGIS.Desktop.Framework.Controls.EmbedableControl.  You can create one of these using the Visual Studio template.      Internally we typically follow the below steps for this pattern. 1. create an internal control and viewModel pair to hold the UI and code behind. 2. create an EmbeddableControl (a view and viewmodel  pair) that hosts and instantiates the control and the control's view model from step1 3. create a DockPane (a view and viewmodel pair) that hosts and instantiate the control and the control's view model from step1. 4. The esri_tasks_embeddableControls daml entry reference the view/viewmodel from step 2.  The "relatedCommand" attribute in that same daml entry references the buttonID that launches the dockpane from step 3.    As you can see, this is an advanced extension pattern that has a certain amount of complexity involved.   I hope this information helps to get you started.    Let me know if you have additional questions.  Narelle ... View more

Hi David,    Sorry for the late reply.  I have been looking at your post and code and have a few comments.   1.  I'm sure you've read the documentation we have about editing annotation and it's special considerations but am including a link here for reference.  (https://github.com/Esri/arcgis-pro-sdk/wiki/ProConcepts-Editing-Annotation)  2.  The API currently doesn't expose the ability to show the yellow "grabhandle" that you see with the built in Move tool (that identifies the feature being moved).  We have identified this as future functionality we would like to add but currently do not have a timeline identified. 3.  The MapTool.AddOverlay function that you are using will create a graphic from the geometry and symbol parameters that are passed.  This is why you see the line being displayed on the screen.   The line is the baseline geometry  of the annotation feature - the geometry that the annotation text lies on.     To see the annotation text on the overlay,  you should use the AddOverlay function that takes a CIMGraphic  https://pro.arcgis.com/en/pro-app/latest/sdk/api-reference/topic27604.html.    The CIMGraphic passed would the CIMTextGraphic of the annotation feature  (found from AnnotationProperties.TextGraphic).  4.  Because you're dealing with annotation and text, it is also important to use the second parameter of that AddOverlay method - the referenceScale.  This can be retrieved from the AnnotationFeatureClassDefinition.  await QueuedTask.Run(() => { var annoFC = _layerAnno.GetFeatureClass() as AnnotationFeatureClass; var annoFCDef = annoFC.GetDefinition() as AnnotationFeatureClassDefinition; _annoRefScale = annoFCDef.GetReferenceScale(); var refScaleUnits = annoFCDef.GetReferenceScaleUnits(); });   So the AddOverlay routine would become  _graphic = AddOverlay(_trackedTextGraphic, _annoRefScale);   5.  Unfortunately there is no MapTool.UpdateOverlay method that supports the moving of text graphics in the manner used in your code.  This is a gap in our API that was found as a result of looking at your post and it will be fixed in the next Pro release.   Thanks for helping to identify this.  6. In the meantime a work around would be to dispose of the previous graphic and create a new one with the CIMTextGraphic at the moved geometry position.  Unfortunately because this is in  MouseMove, the performance may not be as smooth as the standard tool.  Here's a sample of code that could replace your UpdateOverlay call Geometry movedGeometry = null; if (_trackedSide == "up" || _trackedSide == "down") { movedGeometry = GeometryEngine.Instance.Move(_trackedGeometry, x, 0); } else { movedGeometry = GeometryEngine.Instance.Move(_trackedGeometry, 0, y); } lock (_lock) { if (_graphic != null) _graphic.Dispose(); var newGraphic = _trackedTextGraphic.Clone(); newGraphic.Shape = movedGeometry; _graphic = AddOverlay(newGraphic, _annoRefScale); }   I hope this provides some clarification and helps you make progress with your tool.  Please let me know if you have any questions or comments about the above.   Regards Narelle ... View more

Hi Roxana,    Unfortunately these trace options are not currently available in the public API.  I will create an issue to add these in a future release.    regards Narelle   ... View more

Hello,  I don't believe we have anything in the public API that will currently support what you are trying to accomplish with regards to highlighted rows.  We do have an issue in the backlog to add additional API functionality to the attributes pane so I will add this requirement to that list.   We are hoping to address this issue for the next release.    Thanks Narelle ... View more

Hi Karen,  I have taken a look at this, and can duplicate the behavior that you're seeing.  Namely that modifying some map properties - either via some of the API calls or by modifying the CIMMap properties directly - can cause the sketch to be cancelled.   In your scenario because you haven't yet started a sketch this will cause the tool to become deactivated.     Unfortunately, I don't have a workaround at this time.    But can I ask you to explain your workflow as to why you are changing the map's spatial reference in the tool activation.  If I understand your workflow, perhaps I can make a suggestion which will avoid the problem.     thanks Narelle   ... View more