Latest Contributions by GKmieliauskas

Hi, First thing, move 18-19 line before line 12. This is performance issue. Second thing, EditOperation Execute method could be called only once. You call it in a cycle. There is 2 solution methods: - move createOperation inside cycle. - move Execute calling outside cycle. Third thing. Store in 45 line could be used in EditOperation with callback. Mixing of different EditOperation approaches is not legal. You can use Modify method from EditOperation and call Execute after Modify (depending on the way you choose in second sugesstion).  In some cases you can use chained operation. More information here: https://github.com/Esri/arcgis-pro-sdk/wiki/ProConcepts-Editing#performing-edits-in-pro  ... View more

Hi,  How to handle loaded event in WPF here: https://docs.microsoft.com/en-us/dotnet/desktop/wpf/advanced/how-to-handle-a-loaded-event?view=netframeworkdesktop-4.8  You can set ProWindow position in xaml or in code. ProWIndow is derived from Window. In xaml you can use WindowStartupLocation:   <controls:ProWindow x:Class="YourWindowView" xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation" xmlns:controls="clr-namespace:ArcGIS.Desktop.Framework.Controls;assembly=ArcGIS.Desktop.Framework" xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml" xmlns:d="http://schemas.microsoft.com/expression/blend/2008" xmlns:mc="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:extensions="clr-namespace:ArcGIS.Desktop.Extensions;assembly=ArcGIS.Desktop.Extensions" mc:Ignorable="d" Title="Window name" MinWidth="550" WindowStartupLocation="CenterOwner" d:DataContext="{Binding Path=vm.YourWindowViewModel}" SizeToContent="Height" Width="550" >   It has few alternatives. More info here: https://docs.microsoft.com/en-us/dotnet/api/system.windows.window.windowstartuplocation?view=netframework-4.8  In code you can do like this:   var window = new YourProWindow(); window.Left = 100; window.Top = 100; window.ShowDialog();       ... View more

Hi, Use the same approach as in line 8. You can pass to MakeValueArray everything. var lyrCrossings = map.GetLayersAsFlattenedList().OfType<FeatureLayer>().Where(l => l.Parent.ToString() == "Group" && l.IsVisible == true).ToList(); var inputList = Geoprocessing.MakeValueArray(lyrCrossings, secondPath); var args = Geoprocessing.MakeValueArray(inputList, outputPath, "", "", "POINT"); string toolPath = "analysis.Intersect"; var result = await Geoprocessing.ExecuteToolAsync(toolPath, args, environments); If you want to know what exactly takes geoprocessing tool from your layer then you need to execute geoprocessing directly from ArcGIS Pro and copy Python script from History record. ... View more

Hi, Have you tried Query Layers? The description of the query layers is on the same page as your QueryTable link. Just below few lines. Code is very similar. Example below is from ArcGIS Pro SDK samples: private void MakeQueryLayer(string commaSeparatedFields, Table leftTable, Table rightTable) { string fields = string.IsNullOrEmpty(commaSeparatedFields) ? "*" : commaSeparatedFields; var database = leftTable.GetDatastore() as Database; var joinClause = IsLeftOuterJoin ? $"{leftTable.GetName()} LEFT OUTER JOIN {rightTable.GetName()} ON {leftTable.GetName()}.{_leftField.Name} = {rightTable.GetName()}.{_rightField.Name}" : $"{leftTable.GetName()} INNER JOIN {rightTable.GetName()} ON {leftTable.GetName()}.{_leftField.Name} = {rightTable.GetName()}.{_rightField.Name}"; var queryDescription = database.GetQueryDescription($"SELECT {fields} FROM {joinClause}", LayerName); var table = database.OpenTable(queryDescription); LayerFactory.Instance.CreateFeatureLayer(table as FeatureClass, MapView.Active.Map, 0, LayerName); } All sample code here: https://github.com/Esri/arcgis-pro-sdk-community-samples/tree/master/Geodatabase/DynamicJoins  ... View more

Hi, You need to add your cursor file to visual studio project as resource. Instead of "MapExploration.Resource1.red_cursor"   use Properties.Resources.<your_cursor_resource-name>   ... View more