Latest Contributions by HoriaTudosie

Thanks - it works for me too! Great Response! Still a small issue but not related to my issues: The colors of the sliders above look weird: shouldn't be red - something like red, green - something like green, and blue - something like blue? ... View more

Hi Charles, I see now: trans is 50.0 instead of 255! Tx, ... View more

No, is not: From line 20 to line 26 I,m explicitly define the stoke with black color. See, the thing is that this is a template used in line 31, that together with the colorRamp instance form in line 51 the Unique...Def. Now: if we create make the line red: symbol = SymbolFactory.ConstructPolygonSymbol( ColorFactory.GreyRGB, SimpleFillStyle.Solid, new CIMSolidStroke() { Width = 1.5, Color = CIMColor.CreateRGBColor(255, 0, 0, 127) });‍‍‍‍‍‍‍ When running the application, we get: Where we see that the line was correctly defined, but the corresponding checkbox was not enabled. (And no: it is red but not semitransparent!) Note that ConstructPolygonSymbol has another constructor which takes, instead of the first two parameters, a Fill (something) type, in the same way as the stroke. When using that, the fill symbol comes also unchecked! (On my wish list there are also: 1.   Use directly (some sort of) UniqueValuesItems instead of colorRamp and symbolTemplate, as I've mentioned in the second line of my question. 2.   Be able to customize the color of the stroke as well, 3.   And, as I've already mentioned, make the fill transparent (if possible, the stroke as well.) #2 and the () in 3# are optional, but without the rest - is not going to work... ) ... View more

I know by hart that snippet since it is the only one that shows something about creating an UniqueValueRender. However it is limited to MapPoints that do not require transparency, not even color ramps! More details about how I'm using that code - in my other question, here: https://community.esri.com/message/638051-how-to-create-an-uniquevaluerenderer  ... View more

Unfortunately, the solution with AddOverlay is not a good fit: AddOverlay waits for the map to be not busy (long time) while the previous solution was putting everything on the map before finishing updating the base map! I have reverted everything and used your previous suggestion... ... View more

Trying your solution now, which is cleaner - I did not know about AddOverlay method! (How do you remove the geometries added like that!?) Working from home today, - looks a lot slowser because the map remains busy after each zomm for a couple seconds. I had the feg that the previous method (using FeatureLayers) was rendering my symbols before clearing the busy flag... I have to come back to check, or to go to the office to have faster connection... (I also have to stop now for a couple hours...) ... View more

Thank you, However I got so many issues that I've consider a complete different approach: I've created features layers in the project's gdb, added symbollogy of each type (I need two types - so two feature layers, each with its own symbollogy - the easiest approach,) and I'm adding my buffers as geometries (with an EditOperation.) Before that, I've tried everything and got something working (sorry, I don't have the code anymore.) My extension explores a collection of features (roads) that can be paired (Delete segment with Insert segment) automatically - testing the end points and the middle point in a buffer. I'm showing the buffers for visual feedback. When the solution using ExecToolAsync was ready (with lot of delays, flickering, dudes, etc.) I was able to explore max 12-20 features, after them ArcGIS Pro was blocking in a dead-lock (no error, no message, nothing - just waiting forever.) It was not the first issue with ExecToolAsync, so I've decided to stop wasting time and did the research for the above solution. Even so, I'm still using Geoprocessing.ExecuteToolAsync("management.CreateFeatureClass" once I'm starting a new project and is not quite working as expected: private async void AddSketchLayers() {     PointMatchLayer = await AddSketchLayer(Model.LayerPointMatch, true);     PointEmptyLayer = await AddSketchLayer(Model.LayerPointEmpty, false); } private async Task<FeatureLayer> AddSketchLayer(string layerName, bool fill) {     var layerNames = DeltaMap.Map.Layers.Select(l => l.Name).ToArray();     if (layerNames.Contains(layerName))     {         return DeltaMap.Map.Layers.FirstOrDefault(l => l.Name == layerName) as FeatureLayer;     }     SetBusy($"Create {layerName}...");     try     {         var outPath = Project.Current.DefaultGeodatabasePath;         var result = await QueuedTask.Run(async () =>         {             //var workspaceName = $@"in_memory\{layerName}";             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;                     }                 });             var layer = DeltaMap.Map.Layers.FirstOrDefault(l => l.Name == layerName) as FeatureLayer;             if (layer == null)             {                 layer = LayerFactory.CreateFeatureLayer(                     new Uri($@"{outPath}\{layerName}", UriKind.Relative),                     DeltaMap.Map);             }             if (layer != null)             {                 layer.SetDisplayCacheType(DisplayCacheType.None);                 layer.SetSnappable(false);                 layer.SetEditable(false);                 layer.SetSelectable(false);                 layer.SetShowPopups(false);                 var rendererDefinition = new SimpleRendererDefinition                 {                     SymbolTemplate = SymbolFactory.ConstructPolygonSymbol(                         fill                         ? ColorFactory.CreateRGBColor(162, 80, 255, 90)                         : ColorFactory.CreateRGBColor(255, 88, 100, 90),                         fill                         ? SimpleFillStyle.Solid                         : SimpleFillStyle.Null,                         new CIMSolidStroke                         {                             Color = fill                             ? ColorFactory.CreateRGBColor(162, 80, 255, 127)                             : ColorFactory.CreateRGBColor(255, 88, 100, 127),                             Width = 1,                             Enable = true                         }).MakeSymbolReference()                 };                 var simpleValueRenderer = (CIMSimpleRenderer)(layer.CreateRenderer(rendererDefinition));                 layer.SetRenderer(simpleValueRenderer);             }             return layer;         });         return result;     }     catch (Exception ex)     {         MessageBox.Show(ex.ToString());     }     return null; } See lines 56 to 64. Note that I need two Feature Layer, so I call the method AddSketchLayer twice in lines 3 and 4. The test in line 58 is for the first call, the second call adds the layer to the map directly (line(56,) totally unexpected! If I'll have more issue with this code, I'll try to replace the call to ExecToolAsync from line 30 with something more natively... ExecuteToolAsync ... View more

This is what the extension does: Basically, given a road segment, it tries to match another one with complementary operation INSERT/DELETE. The test is done in three points - two at segment ends and one somewhere in the middle. The calculation is always correct and displayed on the bottom of the grid. The display is done only for the user convenience and repeats the buffering with the tool mentioned before. The buffer is about 1/20 of the segment road, and the segment road length is consistent with small streets in an average city. (The units are in Degrees - I would have prefer them in meters to be able to put a cap, but since it is not a real requirement, I can operate also in degrees. The value is something 10^-5, so not very comprehensive...) The picture above is one that succeeds after about 8 trials. I can repeat the attempt clicking the button "Automatic Pairing" on the Delete header. It gets a few seconds to get the disks/circle in some random colors and a few more to change in these standard colors depicted there. But all the previous trials came with no circles, sometimes only with the two filled ones, some other times only with the empty one. When I have three match points - there is only one call to ExecToolAsinc (l2 in the second code block above, is null.) In that situation I can get the picture ready most of the times, but there are also situations when I have to repeat. (Before doing all that, I'm also deleting all previous disks, but I have commented that procedure (line 13) during tests, and it has no effect: public async Task<bool> ClearBufferLayers() {     AutomaticMessage = null;     AutomaticPossiblePair = null;     await QueuedTask.Run(() =>     {         return DeltaLayer.Map.Layers.Where(l =>         {             var b = l as FeatureLayer;             return (b != null) && (b.LabelClasses[0].WhereClause == "[BUFF_DIST]");         });     }).ContinueWith(async t => await QueuedTask.Run(() => DeltaLayer.Map.RemoveLayers(t.Result)));     //await QueuedTask.Run(() => DeltaLayer.Map.RemoveLayers(buffLayers));     return true; } ) I'm using ExecToolAsync because I cannot draw directly on the map. ArcGis Pro does not support GraphicsLayers (or does it?) and I'm not able to create a FeatureLayer on the fly. This is the code I attempt to run a new feature layer in the default geodatabase: private async Task AddSketchLayer(string layerName, bool fill) {     var uri = new Uri($@"{Project.Current.DefaultGeodatabasePath}\{layerName}", UriKind.Absolute);     try     {         var f = await QueuedTask.Run(() => LayerFactory.CreateLayer(uri, DeltaMap.Map));     }     catch     {     } } But it fails! The error is System.ArgumentException, the Exception message is {"Failed to create layer from C:\\Users\\htudosie\\Documents\\ArcGIS\\Projects\\MyProject1\\MyProject1.gdb\\PointMatchLayer."} There is no other detail or tip on how I can fix it. Being able to build that feature layer and adding a render, I would get rid of ExecToolAsinc. I already have the buffer shapes... ... View more

Maybe I'm doing wrong in ArcGIS Pro, because I've started the first application/Extension with the old good habits from pure WPF applications. But usually, you connect the View model in XAML like this: <Grid x:Name="main" >   <Grid.DataContext>         <local:GfxViewModel/>   </Grid.DataContext> (Where Grid may be any control in the page, not necessary the root, and the ViewModel may not be the main one handeled by the DockPaneManager.) This approach, with proper techniques, let the page function in DesignMode as well using the Inversion Of Control pattern (somehow, injecting a corresponding model for RealTime, another for DesignMode and some more for unit tests...)) The problem is that if you associate the same ViewModel with another page in this way, each page creates its own instance, so the data you want to share is different in each instance. What the above code references in line 3 is actually the parameter-less constructor of the ViewModel. You cannot add a parameter, refer a Singleton or a a static reference (although a static resource does the job...) This is where the VMLocator comes. It is actually a static reference that manages VMs. It needs however a place where to instantiate its Singleton. DockPanelManager is not a very good place, because you may need the VM instance in a Tool as well for example! GalaSoft's MVVM Light may instantiate singletons managed by the static resource VMLocator in a top page named APP.XAML. VMLocator is a very complex piece of code - I dare not reproduce it, mostly because of the testing involved. It is a manager that can manage multiple VMs, singletons or not. I already have a solution in the code behind, but I ask for a professional solution if somebody already have put it in ArcGIS Pro. In my extension I have a DockingPanel that handle the main work with the above VM. I open it with a Ribbon Button. I have another DockPanel that I open with another button (in a split of another ribbon button) that displays a Pie Chart (the beginning of a Dashboard,) with the data from the first Panel's VM. Users may activate these buttons in any order, but obviously one of them is wrong. My code behind in the Chart Panel check the instance of the Main Panel and give up if was not instantiated: the panel comes blank. Could come better if it could make the instance first: could display a pie with four equal sectors (Eventually a message) which are the defaults of the DataSource. Will cange as soon as the VM will get notifications (Property Changed) from the first page. But this solution would require instantiating the (same) VM of the Working Panel also in code. This makes the Design Time complicated... (And I don't have a general-enough place where to put the singleton.) (Blocking the button of the Pie Panel until the Working panel opens also works, but then the ToolTip of the button - not mentioning the panel itself - won't come and I'll have to write a manual or help, which makes the User Experience gross...) Note that instantiating VMs in the code behind, which is technically the View, breaks the MVVM pattern, making the design difficult and the testing incomplete! Note also that a DockpaneViewModel is not exactly a ViewModel: it contains an internal static class for the button to open it, with override methods, which you have to trust - not to test... ... View more