Latest Contributions by UmaHarano

I see this issue also. Thanks for reporting this. I will post an update when this gets addressed.   Thanks! Uma ... View more

Hi, If you pick the On the Ground option, the CIM definition of the layer looks like this:   <LayerElevation xsi:type="typens:CIMLayerElevationSurface"> <OffsetZ>0</OffsetZ> <ElevationSurfaceLayerURI>CIMPATH=Map/dc9328b7a8a849d78652499f3fa0ca9e.json</ElevationSurfaceLayerURI> <IsRelativeToScene>false</IsRelativeToScene> </LayerElevation>   In code, you can set these CIM values like this:   var layer = MapView.Active?.Map?.GetLayersAsFlattenedList().OfType<FeatureLayer>().FirstOrDefault(); var surface = MapView.Active.Map.GetGroundElevationSurfaceLayer(); if (layer == null || surface == null) return; await QueuedTask.Run(() => { //Get the layer's CIM Definition var layerDefn = layer.GetDefinition() as CIMFeatureLayer; //Set the LayerElevation properties layerDefn.LayerElevation.ElevationSurfaceLayerURI = surface.URI; layerDefn.LayerElevation.OffsetZ = 0; layerDefn.LayerElevation.IsRelativeToScene = false; //This is important - set the FeatureElevationExpression to an empty string layerDefn.FeatureElevationExpression = string.Empty; layer.SetDefinition(layerDefn); });     If you pick the Relative to the Ground option, there is an additional attribute on the CIM that specifies the attribute to use for feature elevation.   <FeatureElevationExpression>Shape.Z</FeatureElevationExpression>   In code, you set this CIM value like this - (in addition to setting the LayerElevation mentioned above).   layerDefn.FeatureElevationExpression = "Shape.Z";   ... View more

Attached is an addin that creates a Polygon construction tool. This tool implements "ToolOptions". In the Options UI, I added a text box for Tolerance. Then on the Tool activate callback, I used the tolerance provided in the options UI and to set the map's snapping environment's XY Tolerance like this: var snapOptions = Snapping.GetOptions(ActiveMapView.Map); snapOptions.XYTolerance = ToleranceToolOption; Snapping.SetOptions(ActiveMapView.Map, snapOptions);     ... View more

Hi Dave, Is this the info you are looking for?  //Set snapping options via get/set options var snapOptions = Snapping.GetOptions(myMap); snapOptions.IsSnapToSketchEnabled = true; snapOptions.XYTolerance = 100; snapOptions.IsZToleranceEnabled = true; snapOptions.ZTolerance = 0.6; Snapping.SetOptions(myMap,snapOptions); https://github.com/Esri/arcgis-pro-sdk/wiki/ProConcepts-Editing#snapping ... View more

Hi Dave In majority of the cases, the MapMemberPropertiesChangedEvent is fired per layer.  So, MapMembers in the MapMembers list is always the same layer in the majority of the cases.  I am investigating to see if there are any edge cases where this is not true. Regarding the event hint in the changing of the layer name via the Properties page or the Contents pane - that does look like an inconsistency. Thanks for reporting this one! ... View more

Pro 3.2 is expected to be available next week. ... View more

I see this behavior also. I will post back if I have any updates on this. Just curious about the workflow you are trying to achieve with the custom tool - How will you zoom, pan, identify, select?    Will your tool handle all the actions?   ... View more

Hi Here is the method: SetFrozenFieldsAsync Method (TableView)  Sets the specified fields to be frozen in the table view. Frozen fields are promoted to be the first visible fields in the table view and stay visible as the table view is scrolled horizontally. A divider bar is placed between the frozen fields and the remaining fields in the table. The specified list of fields are added to any existing fields that are already frozen. ... View more

You can use the EditOperation.Merge method to merge features programmatically. If you are looking to re-create the "Merge Construction Tool" available with Pro, you can create your own construction tool using the Pro SDK that is similar to what Pro does like this: * Create a Custom Construction tool with options. Here is a wiki with sample code that walks you through this: https://github.com/Esri/arcgis-pro-sdk/wiki/ProGuide-Construction-Tools-with-Options   This ProGuide demonstrates how to create a construction tool with options which allows users to input parameter values to the tool at run-time.  So in this UI you can add logic to pick your features to merge, etc.   ... View more

Button controls have a Pro Style. Can you try adding this style to you button element? Style="{DynamicResource Esri_Button}" ... View more

Hi, Thanks for reporting this. We are investigating this.  ... View more

Hi, You can use the condition attribute for the tool element in your config.daml to disable\enable the tool based on what is selected.  MapSelectionChangedEvent gives you the opportunity to see if the feature you want is selected. Based on that you can set your condition. Here is a ProGuide on how you can implement your own conditions for your workflow:  ProGuide: Code Your Own States and Conditions    ... View more

Hi I am able to reproduce this issue too. It sounds like a bug - I will report this to the dev team. Thanks for reporting this. In the meantime, can you please try this by matching the extension name (case) with what you have in the config.daml fileExtension attribute value?   Thanks! Uma ... View more

Hi, Just a few questions to clarify the issue - 1. Does your custom item have a file extension of gsi? 2. On disk, if the file is .GSI, then it doesn't show up in Pro with the corresponding file image. If on disk, the file is .gsi, then it shows up in Pro with the corresponding image. Is that correct? 3. In config.daml file of your add-in, can you please send me the fileExtension attribute value?   Thanks! Uma   ... View more