Select to view content in your preferred language

ArcGIS Pro 3.0 Dimensioning SDK - graphic elements option settings

796
5
01-25-2023 03:36 AM
DirkTillmanns
Occasional Contributor

Hello,

We come across in the ArcGIS Pro 3.0. Dimension API for fatal errors. All methods for setting the visibility of graphic elements throw an "Ot of range exception". A Pro enumeration is passed, so you can hardly do anything wrong. This means that the functionality is completely unusable!

  • SetDimensionExtensionOption
  • SetDimensionLineOption
  • SetDimensionMarkerOption

DirkTillmanns_0-1674646000877.png

https://pro.arcgis.com/en/pro-app/latest/sdk/api-reference/topic21935.html

At esri colleagues, can you help?

Best regards

Dirk

 

5 Replies
DirkTillmanns
Occasional Contributor

I implemented a workaround that implements the option settings directly through entries in the row fields of the feature. But that is not an acceptable way.

0 Kudos
DirkTillmanns
Occasional Contributor

Did not work because of enum change.

0 Kudos
DirkTillmanns
Occasional Contributor

Hallo Esri colleagues,

I could not believe! 😰  Esri changed an existing enumeration with the version change from 2.9 to 3.0. 

And even worse! 😝 This is an enumeration whose values ​​are written directly into a field of a DimensionFeature.

This means that all data recorded with 2.9 is broken.

DirkTillmanns_0-1674671008574.png DirkTillmanns_1-1674671049754.png

 

 

0 Kudos
CraigWilliams
Esri Contributor

Datasets created in ArcGIS 2.x values are not broken. The values for dimension field integer values are the same between 10.x, ArcGIS Pro 2.x, and ArcGIS Pro 3.x dimensions. The CIM enum was incorrect in ArcGIS Pro 2.x though, so in ArcGIS Pro 2.x we converted between old and new integers when writing the field values into dimension feature classes. At ArcGIS 3.0, a breaking change release, we took the time to fix this discrepancy and matched the CIM enum integers to the persisted values. Unfortunately when we did this we missed a logic error in validation of input, which is why Out of Range is being reported. This Out of Range issue will be fixed in ArcGIS Pro 3.1 and we'll look to backport it to a 3.0 patch if possible.

0 Kudos
DirkTillmanns
Occasional Contributor

Hi Craig, 

Could you please take a look at the following post. Same place, new error.

Thanks

https://community.esri.com/t5/arcgis-pro-sdk-questions/setting-any-dimensioning-options-programmatic...

0 Kudos