Latest Contributions by Wolf

Your finding is correct ContextMenuDataContext  is null for the Can method for DelegateCommands.  I will check with the development team on this issue.  However, if you intend to use this function to control visibility of your menu button i would recommend to use a condition instead. When i duplicated your issue i was only interested in showing the context menu button when a feature layer has been selected.  So i added the esri_mapping_featureLayerSelectedCondition condition to my button: <controls> <!-- add your controls here --> <button id="TestContextMenu_LayerContextMenu_Items_Button1" caption="Show Selected FLyr Name" className="TestContextMenu_Module:OnMenuButtonClick" loadOnClick="true" keytip="B1" condition="esri_mapping_featureLayerSelectedCondition" smallImage="Images/GenericButtonGreen16.png" largeImage="Images/GenericButtonGreen32.png"> <tooltip heading="Menu Button 1">ToolTip<disabledText /></tooltip> </button> </controls>‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ And now the context menu honors the state of condition i added:  Below is the context menu when a feature layer has been selected: and here is context menu when a raster layer has been selected: You can find more conditions here:  https://github.com/Esri/arcgis-pro-sdk/wiki/DAML-ID-Reference-ADMapping.daml#conditions ... View more

When you implement a dockpane using the Pro SDK it supports MVVM (Model - View - ViewModel) out of box.  You can check out this video (starting at minute 20:00 of the video) to get an overview of MVVM in the Pro SDK: https://www.youtube.com/watch?v=5PgaeZycWXc What this means is that the Pro SDK Item Template for DockPanes creates multiple files in support of MVVM for you.  These files are used for: The View (or UI): Dockpane1.xaml (and included with the XAML is the usually hidden Dockpane1.cs file containing the partial class implementation of the Dockpane1View / UserControl class).  If you make any changes to the View you ONLY make these changes in XAML.  You would not make any changes in the code behind for the View (Dockpane1View.cs file) when you are coding using the MVVM programming pattern .   The ViewModel (or business logic, code behind): Dockpane1ViewModel.cs contains the actual business logic and the properties to exchange data at runtime with the View using data binding.  In MVVM this is were all code (business logic) goes, including the properties (which must be public) that are 'data bound' to the View (UI implemented in XAML)  Looking at your code snippet I see that you mixed MVVM with a non MVVM pattern.  To implemented a command using the MVVM pattern, you have to utilize what is known as the ICommand pattern.  There a plenty of examples under the Pro SDK community sample github repo, but you can search for BrowseCommand in the UploadItem sample and you find the XAML implementation here: arcgis-pro-sdk-community-samples/UploadItem.xaml at f5f9dda18efa173a56d128f3ea64ca34ac3f68a9 · Esri/arcgis-pro-sdk-commu…  and the business logic for the BrowseCommand button is here: arcgis-pro-sdk-community-samples/UploadItemViewModel.cs at f5f9dda18efa173a56d128f3ea64ca34ac3f68a9 · Esri/arcgis-pro-sd…  ... View more

I tried the Mvvm version of ProWindow as well and was not able to duplicate the issue you reported.  i am using 2.5 of the Pro SDK. ... View more

I tried this using a Modal ProWindow and didn't experience the hang:  and the selected polygon is flashed as expected, using the code snippet below. try { var oid = long.Parse(ObjectId.Text); var layerName = FeatureLayerName.Text; var lineLayer = MapView.Active.Map.GetLayersAsFlattenedList() .OfType<FeatureLayer>() .Where(lyr => lyr.Name == layerName).FirstOrDefault() as FeatureLayer; await QueuedTask.Run(() => { MapView.Active.FlashFeature(lineLayer, oid); }); } catch (Exception ex) { MessageBox.Show($@"Exception: {ex.Message}"); } ‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ I will try MVVM next, but i can't imagine that this makes a difference.  Try surrounding your code with a try ... catch ... just in case there's issues with code itself. ... View more

I used the following snippet to check if a column value of a Row is null: foreach (var field in fields) { var val = row[field.Name]; if (val is DBNull || val == null) continue; ... }‍‍‍‍‍‍ the code is used in this sample:  https://github.com/Esri/arcgis-pro-sdk-community-samples/blob/2d6a30e2597c7a0079ae65b182f60a77e79aaef7/Map-Exploration/CustomPopup/CustomPopupTool.cs The sample has to ignore null columns.   ... View more

Hi Marvis,  I added a sample showing how to implement a modal ProWindows dialog.  https://github.com/Esri/arcgis-pro-sdk-community-samples/tree/master/Framework/ProWindowMVVM ... View more

I duplicated the problem you were seeing.  The property is not showing the correct value, which should be OSA and DBMS.  I tested in the current alpha version of 2.6 and it's a bug in that version as well.  I reported to issue to the GeoDatabase team.  I will give  an update if i hear of a fix or workaround. Thanks, Wolf ... View more

I posted a new sample that illustrates a 'draping' on ground surface solution for polygons: https://github.com/Esri/arcgis-pro-sdk-community-samples/tree/master/Map-Exploration/OverlayGroundSurface ... View more

Hi Justin,  i managed to get the 'draping' of polygons to work as well, however, i ran into a few issues.  I will try to publish my sample on ArcGIS Pro SDK Community Samples tomorrow, but in essence the algorithm works like this: i take the polygon to create a 'fishnet mesh' from which i then create a [triangle] MultiPatch geometry.  Finally I pass the MultiPatch geometry to GetZsFromSurfaceAsync in order to get the elevation for all MultiPatch nodes set to the proper elevation value.  Quite some work for a workaround, but the result looks like this:   ... View more

Hi Justin,  I managed to get points and lines to work so far.   Points are straight forward (just call GetZsFromSurfaceAsync using the point geometry), but for lines, the trick for the workaround is to 'densify' the polyline before you pass the geometry to GetZsFromSurfaceAsync.  This way each vertex will be elevated to the proper Z value.  Below is the snippet i used in my test tool: protected async override Task<bool> OnSketchCompleteAsync(Geometry geometry) { var polyline = geometry as Polyline; if (polyline != null) { var sR = polyline.SpatialReference; // make more vertices ... using tolerance to cover projected / non-projected coord systems var denseDistance = sR.XYTolerance * 1000; var denseLine = GeometryEngine.Instance.DensifyByLength(polyline, denseDistance) as Polyline; var result = await ActiveMapView.Map.GetZsFromSurfaceAsync(denseLine); if (result.Status == SurfaceZsResultStatus.Ok) { _ = QueuedTask.Run(() => { var movedZup = GeometryEngine.Instance.Move(result.Geometry, 0, 0, 1) as Polyline; ActiveMapView.AddOverlay(Module1.MakeCIMLineGraphic(movedZup)); }); } } return true; } ‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ Depending on the resolution of your surface you might have to elevate the line above the surface because Pro might obscure parts of the lines when you zoom out.  Below is a screenshot of my test where i placed first two points (the Pushpins) and then a line between those two points (i only digitized the start & end points): As i mentioned above once you zoom in the line will not be obscured any more.  Below a screen shot of the line's left end viewed from the opposite side: i haven't figured out the polygon 'draping' yet, but i will finish that and the sample next week. - Wolf ... View more

Hi Justin,  I think Uma is correct as there is no direct method to do this, however, you can look at this method: GetZsFromSurfaceAsync as a workaround. This method takes your geometry and sets the Z values to elevation surface Zs.  You can then add the output 3D geometry to as an overlay graphic.  I will add a sample to community samples that will do this.  Hopefully later today...  - Wolf ... View more