"}],"short_description":"Learn how you can migrate your legacy SketchEditor code to leverage the rich capabilities in the new GeometryEditor.","flexible_content":[{"acf_fc_layout":"content","content":"Code examples for this blog are written in C# using ArcGIS Maps SDK for .NET; but the Geometry Editor concepts all apply to Java, Kotlin, Qt, and Swift.<\/em><\/p>\n The 200.2 release<\/a> of the ArcGIS Maps SDKs for Native Apps paves the way to a brand new GeometryEditor<\/a> in .NET. Learning from developing the SketchEditor<\/a>, we made significant improvements in its replacement. It is now built from the same core C++ to provide your applications a consistent, intuitive, easy to use, highly customizable, more reliable, and performant editor. This single core implementation will enable us to fulfill your most requested enhancements, like snapping and curve editing, more efficiently across all the Native SDKs.<\/p>\n In this article, I will cover the following topics to help you decide when and how to navigate the code migration process for .NET:<\/p>\n The SketchEditor<\/em> is deprecated in the 200.2 release, replaced with an API that has a set of comparable functionalities.<\/p>\n To name a few, the GeometryEditor <\/em>enables you to:<\/p>\n You will notice that the start methods take remarkably similar parameters. There are two main groups: Draw<\/em><\/strong>, creates a new geometry based on type, and edit<\/em><\/strong>,<\/em> updates a specified geometry. The GeometryEditor<\/em> in support of these operations responds to the same map interaction using mouse, stylus, or touch devices; and similar routine calls for insert, move, delete, and replace.<\/p>\n The following table highlights the equivalent support for drawing and editing in the GeometryEditor<\/em>.<\/p>\n\n
<\/a>Functional equivalence<\/u><\/strong><\/h2>\n"},{"acf_fc_layout":"content","content":"
\n