Latest Contributions by CharlesMacleod

‎08-21-2019

I suspect this is the root of your original problem: var rowCursor = layer.Search(myGeometry, SpatialRelationship.Crosses); You are using a recycling cursor. Change to a non-recycling cursor (access this off the feature class). With a recycling cursor, repetitive calls to op.Modify with rowcursor.Current will get overwritten by the following "current" feature. (note: the last feature in your selection was probably getting successfully modified). //This is a problem with a recycling cursor when in a loop. cutOperation.Modify(rowCursor.Current, fkzFieldIndex, "MyNewFKZ");

‎07-19-2019

Than, start here: ProConcepts-Framework#introduction-to-daml-desktop-application-markup-language

‎07-18-2019

Matt, this is a bug. It will be fixed in the next release - 2.5

‎07-18-2019

Than, you are almost there 😉 You have some copy-paste baggage. Change this '<updateModule refID="esri_mapping">' to this '<updateModule refID="esri_geodatabase_module">' and you will have it.

‎07-17-2019

Than, This is how I would find a context menu id by way of example. Let's assume that you want to add a new item to the "Databases" context menu in Catalog pane (sorry, I am not familiar with "Research Data" context menu) First, make sure this option is checked on: Go to the context menu you are after and hover over one of the core buttons that is on it (in my example I use "Databases" folder context menu): With the "Show Command IDs" option checked on you get the daml id for the particular button you are hovering over displayed in its tooltip. Go to: https://github.com/esri/arcgis-pro-sdk/wiki/ArcGIS-Pro-DAML-ID-Reference In your case I would try "ADGeoDatabase.daml" first - which also happens to be the .daml file I will use to find the "Databases" context menu. Click on the "Click this link to view ADGeoDatabase.daml" link on the github to get to the "raw" daml. Hit Ctrl-F and type in the daml id you captured from the desired context menu button: Step through occurrences of the daml id until you get to the containing menu you are after: Cycle through the other daml files if you don't get a hit in ADGeoDatabase.daml. Record the daml id (GDBContainerMenu in my example).

‎07-17-2019

I was answering this: >>My question is how come SDK automatically updated to 2.4??<<

‎07-17-2019

Hi Naresh, this is explained here: ProGuide-Installation-and-Upgrade#upgrade-arcgis-pro-sdk-for-net

‎07-07-2019

sounds like the Microsoft Visual C++ redistributable package is missing from your server machine https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads

‎06-17-2019

Max, the issue to me looks like you are not specifying a cell size. The resulting cell size of the raster is 10600614 which matches the dimension of the raster. I do not know the significance of that number (i.e. why is it used as the default cell size). However, if I do specify a cell size explicitly (eg "90" or "180" ) then the extent of the layer is correct (as, in, it is a proper extent). As the cell size, in this case because of the projection being used, is in decimal degrees and the WGS projection is wider than it is tall, I assume that the maximum possible cell size will be "180" while still retaining a "real" spatial extent. For example, using your same settings and a cell size of 180:

‎06-14-2019

Hi Max, the layer extent looks bogus:

‎06-11-2019

I cannot reproduce. My results using 2.4: SR Domain, MapView Extent, layer "QueryExtent" Initial extent: Zoom to layer extent Pan to date line (or approx) with "Enable wrapping around the date line" enabled layer properties: map properties:

‎05-31-2019

Max, Unfortunately, it looks like ProportionalRenderer Recalculate is not currently supported in the public API. We will add recalc support in 2.5. I will update the API reference for 2.4. Thanks for bringing this to our attention.

‎05-09-2019

So Max, I have looked closely at this and discussed with the original developer.This is designed behavior. Please use GetOverlayControls to examine which controls are already on the overlay. The returned UIElements can then be queried for their size and placement information [on the overlay]. For example, perhaps you have a preferred placement and prior to adding your control you want to detect if a control (perhaps placed by Pro or another add-in) already occupies that "space". Based on your examination of the existing overlay controls, your logic could adjust your default position accordingly, alter ZOrder, etc. It is not intended that you cast the controls to their underlying type. Simply use them "as" UIElement. Cast to FrameworkElement also, if needed. If you do need reference to your control "later on" you should hold a reference to it. We will update the API reference for AddOverlayControl and GetOverlayControls for 2.4

‎05-07-2019

Max, this could be a bug. I'll look into it.

‎02-21-2019

correct.

Online Status	Offline
Date Last Visited	yesterday

My Ideas

Latest Contributions by CharlesMacleod

Re: Split polygon and modify its attributes

Re: Daml id for catalog folder context menu

Re: Project Referenced DLL not Extracting from .esriAddinX

Re: Daml id for catalog folder context menu

Re: Daml id for catalog folder context menu

Re: Can Add in developed in 2.3 works for 2.4

Re: Can Add in developed in 2.3 works for 2.4

Re: PackageAction seems to have no effect when building Add-In

Re: MapView.Extent is wrong on spatial reference change

Re: MapView.Extent is wrong on spatial reference change

Re: MapView.Extent is wrong on spatial reference change

Re: API for proportional renderer 'Refresh values' command

Re: MapView.GetOverlayControls returns wrappers instead of added controls

Re: MapView.GetOverlayControls returns wrappers instead of added controls

Re: Is the default drop handler muteable?

Re: Persist Application settings across multiple P...

Re: MapTool - frozen ribbon bar during geometry pr...

Re: MapTool - frozen ribbon bar during geometry pr...

Re: MapTool - frozen ribbon bar during geometry pr...

Re: ArcGIS Pro Add-In targeting .net6 migration ne...