Latest Contributions by CharlesMacleod

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