Latest Contributions by CharlesMacleod

Your code, as such, looks ok. The alpha 3 snapshot likely has bugs. You should have access to the alpha 4 snapshot otherwise please re-try on 1.4 final (available dec, jan). ... View more

Benoit, this is not possible until 1.4. Then you can derive from ArcGIS.Desktop.Framework.Controls.ProWindow which will give you what you need.  ... View more

We will look at supporting this for next release. ... View more

I cannot reproduce your error. I opened a new project with the World Topo base map. Can you change your code as follow please: (this will allow you to catch the exception):  protected async override void OnClick() {      try {        await QueuedTask.Run.... Also, is there a base map currently drawn in your project or a blank map display? Is the map 2D or 3D? ... View more

Sounds like a timing issue. That is, running on the VM is changing the sequence of execution in the Add-in. From the exception you are making an Async call that you are not awaiting. That async call is failing when you are running on the VM (but I have no idea why). If you use the debugger and look at the inner exceptions property it may give you the actual exception that faulted the task.  That said, if you do "await" the async call you can bracket it with a standard "try { } catch" block to trap the exception. I will need to see your code to assist further. ... View more

Hi Horia, so see if this helps: Basically, when trying to reverse engineer what is in the CIM - especially the symbology - it is useful to look at the XML in the debugger. So to see how the fill is handled in a polygon symbol, for example, we can use the factory to make a symbol and then disect its parts like so: CIMStroke outline = SymbolFactory.ConstructStroke(CIMColor.CreateRGBColor(0, 0, 0, trans), 2.0, SimpleLineStyle.Solid); CIMPolygonSymbol fillWithOutline = SymbolFactory.ConstructPolygonSymbol(ColorFactory.RedRGB,     SimpleFillStyle.Cross, outline); var xml = fillWithOutline.ToXml(); Then we can set our breakpoint right after the line: "var xml = ....." (or right after). Now we can inspect the symbol: The basic structure is like so: An outline and two hatch fills in this case and we can inspect the hatch fills to see how they are made also. Okay, so now we will use this knowledge in our code to allow us to customize some of the symbol properties. I am using the same "Renderer From Scratch" sample as previously in the other post - https://github.com/Esri/arcgis-pro-sdk-community-samples/tree/master/Map-Authoring/CIMExamples - modifying "CreateCIMRendererFromScratch.cs": First a method to make a custom hatch fill: internal static CIMFill ConstructHatchFillEx(CIMStroke stroke, double angle, double separation, double transparency) {       return new CIMHatchFill() {            Enable = true,            Rotation = angle,           Separation = separation,          LineSymbol = new CIMLineSymbol() { SymbolLayers = new CIMSymbolLayer[1] { stroke } }      }  ; } Second, a method to make a custom polygon symbol: internal static CIMSymbol ConstructPolygonSymbolEx(IEnumerable<CIMFill> hatchPattern, CIMStroke outline = null) {          List<CIMSymbolLayer> symbolLayers = new List<CIMSymbolLayer>();         if (outline != null)             symbolLayers.Add(outline);         foreach (var fill in hatchPattern)              symbolLayers.Add(fill);         return new CIMPolygonSymbol() { SymbolLayers = symbolLayers.ToArray() }; } Now, some code that uses it: var trans = 50.0;//semi transparent CIMStroke outline = SymbolFactory.ConstructStroke(CIMColor.CreateRGBColor(0, 0, 0, trans), 2.0, SimpleLineStyle.Solid); //Some different strokes to play with var dash = SymbolFactory.ConstructStroke(CIMColor.CreateRGBColor(255, 170, 0, trans), 1.0, SimpleLineStyle.Dash); var solid = SymbolFactory.ConstructStroke(CIMColor.CreateRGBColor(255, 0, 0, trans), 1.0, SimpleLineStyle.Solid); var dashDot = SymbolFactory.ConstructStroke(CIMColor.CreateRGBColor(85, 255, 0, trans), 1.0, SimpleLineStyle.DashDotDot); //Some different hatch fills to play with //Mimic cross hatch CIMFill[] crossHatch = {      ConstructHatchFillEx(dash, 0.0, 5.0, trans),      ConstructHatchFillEx(dash, 90.0, 5.0, trans) }; //Mimic diagonal cross CIMFill[] diagCross = {      ConstructHatchFillEx(solid, 45.0, 5.0, trans),      ConstructHatchFillEx(solid, -45.0, 5.0, trans) }; CIMFill[] diagonal = {      ConstructHatchFillEx(dashDot, 45.0, 5.0, trans) }; //Now we will use them var alaska = new CIMUniqueValueClass() {     Values = alaskaValues.ToArray(),     Label = "Alaska",     Visible = true,     Editable = true,     Symbol = new CIMSymbolReference() { Symbol = ConstructPolygonSymbolEx(crossHatch, outline) } }; classes.Add(alaska); etc, etc. Note: I wrote a blog post on GeoNet about the CIMViewer - https://community.esri.com/groups/arcgis-pro-sdk/blog/2016/08/04/arcgis-pro-cim-viewer a sample you can download from here: https://github.com/Esri/arcgis-pro-sdk-cim-viewer There are instructions on the github on compiling it, etc. It is an Add-in. Once installed you can manually set the properties, etc. you want on the layer or map via the UI and then inspect the CIM with the CIMViewer to see which properties, etc. you need to set in your code to automate what was done with the UI. ... View more

I took a look at the colors I generated in the code. The Color Editor looks correct in my scenario: var trans = 50.0;//semi transparent var alabamaColor = CIMColor.CreateRGBColor(255, 170, 0, trans); ... View more

Horia, it looks like the outline is missing from your symbol. Take a look at this: https://github.com/esri/arcgis-pro-sdk/wiki/ProSnippets-MapAuthoring#how-to-construct-a-polygon-symbol-of-specific-color-fill-style-and-outline I am not sure about your transparency issue. I will take a look at this. ... View more

Ted, try this: https://github.com/esri/arcgis-pro-sdk/wiki/ProSnippets-Geodatabase#opening-an-enterprise-geodatabase-using-sde-file-path ... View more

Clarification: >>>In the case of two or more Add-ins referencing a copy of the same assembly, the first Add-in to ~load~ will load that assembly<<< In the case of two or more Add-ins referencing a copy of the same assembly, the first Add-in to ~use~ that assembly will load that assembly. ... View more

You will have to maintain a list of the graphics you add. Each call to AddOverlay returns an IDisposable. When you dispose that disposable the graphics associated with it are cleared. A convenient place to cache the graphics is your Module (something like internal static List<IDisposable> MyGraphics { ..... }). See https://github.com/Esri/arcgis-pro-sdk-community-samples/tree/master/Map-Exploration/OverlayExamples ... View more

I suggest moving this bit outside of the QueuedTask.Run lambda: var parameters = Geoprocessing.MakeValueArray(                  outPath, layerName, "Polygon", null, "No","No", DeltaLayer.Map.SpatialReference.Wkid);              //var env = Geoprocessing.MakeEnvironmentArray(workspace: workspaceName);              var cts = new CancellationTokenSource();              await Geoprocessing.ExecuteToolAsync("management.CreateFeatureClass",                  parameters, null, cts.Token, (eventName, o) =>                  {                      switch (eventName)                      {                          case "OnValidate":                              if (((IGPMessage[])o).Any(it => it.Type == GPMessageType.Warning ||                                                              it.Type == GPMessageType.Error))                              {                                  {                                      var errorsOrWarnings =                                          ((IGPMessage[])o).Where(it => it.Type == GPMessageType.Error).ToArray();                                      if (errorsOrWarnings.Any())                                      {                                          var e = errorsOrWarnings.Select(err => err.Text).ToArray();                                          MessageBox.Show(string.Join(@"  ", e));                                          cts.Cancel();                                      }                                  }                              }                              break;                      }                  });  ... View more