Latest Contributions by CharlesMacleod

Hi Luke, We have to edit the unique value renderer itself, once it has been made. I have provided some code below. Note: I encourage you to look at the samples for the CIM at https://github.com/esri/arcgis-pro-sdk-community-samples/tree/master/Map-Authoring/CIMExamples. I based the code snippet below on the source code in 'CreateCIMRendererFromScratch.cs'. It uses the U.S. States dataset available with the samples. internal class SetLabelsOnUniqueValueRenderer : Button {         protected async override void OnClick() {             var usStatesLayer =                 MapView.Active.Map.GetLayersAsFlattenedList().FirstOrDefault((fl) => fl.Name == "States") as                     FeatureLayer;             if (usStatesLayer == null) {                 MessageBox.Show("Please add the 'States' layer to the TOC - with a 'STATE_NAME' field containing state names.", "Cannot find US States");                 return;             }             //make a unique value renderer             await CreateUniqueValueRendererOnStatesAsync(usStatesLayer);             SetLabelsOnStatesRendererAsync(usStatesLayer);         }         private Task CreateUniqueValueRendererOnStatesAsync(FeatureLayer fl) {             return QueuedTask.Run(() => {                 var uvrDef = new UniqueValueRendererDefinition() {                     ValueFields = new string[] {"STATE_ABBR"},                     SymbolTemplate = SymbolFactory.DefaultPolygonSymbol.MakeSymbolReference(),                     //Simple ramp                     ColorRamp = new CIMLinearContinuousColorRamp() {                         FromColor = CIMColor.CreateRGBColor(0, 255, 0, 60),//Green, partially transparent                         ToColor = CIMColor.CreateRGBColor(255, 0, 0, 60),//Red,  partially transparent                         ColorSpace = new CIMICCColorSpace() {                             URL = "Default RGB"                         }                     }                 };                 fl.SetRenderer(fl.CreateRenderer(uvrDef));             });         }         private Task SetLabelsOnStatesRendererAsync(FeatureLayer fl) {             return QueuedTask.Run(() => {                 var renderer = fl.GetRenderer() as CIMUniqueValueRenderer;                 //A UniqueValue renderer has one or more CIMUniqueValueGroups. In this example                 //there is only one CIMUniqueValueGroup (otherwise use a 'foreach(var group in ....)'                 var group = renderer.Groups[0];                 //Each group has one or more CIMUniqueValueClasses - in this case we have one class per                 //STATE_ABBR value. Note: The default value and label are on the renderer itself                 //(renderer.DefaultLabel, renderer.DefaultSymbol) and are NOT in a class.                 foreach (var valClass in group.Classes) {                     //Each CIMUniqueValueClass has a Label (what you are after 😉 and an array of CIMUniqueValues                     //As our values are unique, we have one CIMUniqueValue per class.                     //Get its field value (read from STATE_ABBR) and change the label to be the state name                     if (valClass.Values[0].FieldValues[0] == "AK")                         valClass.Label = "Alaska";                     else if (valClass.Values[0].FieldValues[0] == "AL")                         valClass.Label = "Alabama";                     else if (valClass.Values[0].FieldValues[0] == "AR")                         valClass.Label = "Arkansas";                     else if (valClass.Values[0].FieldValues[0] == "AZ")                         valClass.Label = "Arizona";                     //etc,etc                 }                 fl.SetRenderer(renderer);             });         }     } ... View more

The easiest way would be to create the layer using LayerFactory and then apply the symbology to the layer (you just created) using Geoprocessing.ExecuteToolAsync() and the layer file. Something like: var gpresult = await Geoprocessing.ExecuteToolAsync("ApplySymbologyFromLayer_management", new string[]                       {theNewLayerName,@"C:\Location\my_layer_file.lyr"}); Here are some links that might help: Apply Symbology From Layer Performing Geoprocessing Create and Add a Layer to the Active Map ... View more

Hi Ted, Good question. Comes down to priorities basically - we templatized the most commonly used controls (20 templates at 1.2) and the controls that are more obscure we did not. If lots of people want to use checkboxes or spinners on custom tabs we can look at adding templates for them. Otherwise, as you noted, just add them by hand. On the core tabs they are rarely used. ... View more

Hi Shohei, So let me also provide some guidance. First: the documentation you reference is not clear on use of DelegateCommands and we need to do a better job of explaining them and we will do that for 1.2. Second: the DelegateCommand update must be a property, not a method. It must be a property that returns bool. You can actually see that in the Module1.cs class file that Thomas points out in the sample in his reply. This is a subtlety that is not clearly documented. So, to get your code working please try this implementation: internal static void OnMyCustomButtonClick() {             System.Diagnostics.Debug.WriteLine("OnClick called");         }         internal static bool CanOnMyCustomButtonClick {             get {                 System.Diagnostics.Debug.WriteLine("OnUpdate called");                 return true;             }         } Notice that CanOnMyCustomButtonClick is a bool property. Also, I have not used QueuedTask as this is not really necessary and would be inefficient in the Update property given the frequency with which it is called but I get it that you were probably just experimenting with different API characteristics and what-not in your code. Last, to a point Thomas raises with regards to conditions and also an Update implementation. Use of the condition in daml is much more efficient than coding update logic (whether via an OnUpdate override or a "Can..." update property. However, if you do have both, the condition in daml and are updating your enabled state via Update code, then the Update code wins with one exception: The initial enabled state of the button as shown on the ribbon. Before the button has been clicked, the Framework will use the condition in the daml to show its initial enabled state. Once the button has been clicked then the button state is controlled by its Update logic and the condition is ignored. You can observe this behavior with your implementation: Return false from your update property and keep your "esri_mapping_onlyFeatureLayersSelectedCondition" condition in the DAML. Before clicking the button, select and unselect a feature layer in the TOC. You should notice the button's enabled state toggling based on the condition true/false. Once you click the button it will always be disabled regardless of the condition. (Note also that your OnClick logic is never called....why?) This would be akin to coding this for an OnUpdate override: protected override void OnUpdate() {             this.Enabled = false;//disable the button the moment it is clicked.         } ... View more

Hi Shohei, To add the ids to your project use the ArcGIS Pro SDK for .NET Utilities, Pro Generate DAML IDs utility. It is shown here. After you have run it, the ids will show up in Intellisense within a csharp or vb code window. At 1.2 we will include a complete listing of DAML ids on the  ArcGIS Pro SDK wiki ... View more

Hi Joseph, I wrote one for you. Please go to the Pro community samples on the github at https://github.com/Esri/arcgis-pro-sdk-community-samples/tree/master/Geometry/CoordinateSystemDialog There is no API call currently to get the list of SpatialReferences so I had to use arcpy.ListSpatialReferences. We will look at adding that capability into the DotNET API for Pro at 1.3 ... View more