Latest Contributions by LucasDanzinger

Hi Adam-  The two primary drivers for deprecation were lack of uptake on the project from customers and an outdated reliance on OpenGL, which is deprecated in the Apple ecosystem. In theory, we could have rewritten or refactored the project to support Metal, but it would have been a significant undertaking. Given the lack of feedback we've had on the project, we made the decision to deprecate it. There's unfortunately no alternative, short of considering using the Swift or Kotlin SDKs with their AR Toolkits. If this project is important to you and you'd like to discuss further, please reach out to me in a direct message and perhaps we can get on a call to discuss further. Thank you, Lucas ... View more

Hello-   I spoke with the team, and they confirmed that currently, when you create a circle ellipse, it will contain 36 vertices, regardless of scale. It's interesting that the polygon appears to become less dense when you "save" it. Can you provide any details about how you are saving it? Are you just calling toJson on the output geometry? Is there a simplification or any other process in there? It would be interesting to inspect the json at the various stages of serializing/deserializing and see how it differs from the geometry in the debugger. ... View more

I'm not sure on the circle/rectangle question. The interaction is baked in for press->drag->release, without any real programmatic hooks exposed, so no ideas are jumping out immediately. I will need to chat with the team to see if there are any potential workarounds, or if we need an enhancement request for it.   As for saving, there are probably a number of ways to do it. Are you looking to save just the geometries, or the rendering and attribute information as well? The solution could be as simple as outputting the geometry JSON for each geometry you create, and then iterating through this and displaying graphics for each. You could also look at using feature collections, which allow for adhoc data creation, similar to graphics, but are persistable. For that, maybe you could take inspiration from this "markup layer" which we implemented in an example app. This layer subclassed feature collection layer and read json data, applied symbology overrides, etc https://github.com/Esri/dynamic-situational-awareness-qt/blob/main/Shared/markup/MarkupLayer.h You can also create mobile geodatabases in the native SDKs. That might be a bit more than you need, but you can create a new feature table, add it to your geodatabase, and add features with your geometries to your table https://developers.arcgis.com/qt/cpp/api-reference/esri-arcgisruntime-geodatabase.html#createAsync  ... View more

Hello -    Could you provide a video and steps to reproduce? I'd like to test it out on my end.   -Lucas ... View more

I believe the exportImage is going to require a MapView to draw on screen for it to work. Can you provide details on your workflow as to why the shown pattern is necessary for your use case so we could better understand? ... View more

Thanks Duncan. We've heard a few other people asking about web support, but when asked for specifics, we didn't get a lot of details. It seemed like people were more wondering if it's an option, rather than having projects where they had this requirement. One of the main questions I have is whether organizations want to build 1 app that runs on mobile, desktop, and web, and if so, what are some examples or use cases? Often times, the expectations of capabilities, workflows, and certainly UX change drastically between those mediums. Alternatively, is it more that you might build separate mobile, desktop, and web apps, but that you like being able to use the same technology to build those apps? ... View more

Hey Duncan, thanks for splitting this question out 🙂   It's something we have thought about, but there are significant technological hurdles that we would need to solve to make it happen. This is primarily driven by the fact that our SDK is driven fully by the Native SDK's Runtime Core C++ library. Web would require us to use JavaScript API as well, or possibly WebAssembly. The logistics of either of those options have lots of unknowns and work related to them. Given that, I see the chances of this happening in the near term as being pretty low. However, we will continue to monitor this post and discuss with customers to understand the need for this.   Thanks, Lucas ... View more

Hey Duncan, It might be better to post this as a separate question, just to keep things tidy. I think some individuals and orgs may have more interest in Web or Windows, and the amount of work to bring them to life is significantly different. ... View more

Windows is something we've looked at and are considering, but are currently blocked on Flutter supporting the PlatformView on Windows - https://github.com/flutter/flutter/issues/31713. This is needed to render the native map view.   For anyone out there interested in Windows deployment, please reach out so we can gauge the level of interest. I'd also like to hear about types of devices and applications you all are looking to build. Our early investigation of desktop platforms suggests that Flutter may not have as rich of a suite of desktop tooling as a .NET WPF app would, but touch screen surface or toughbook style apps may do just fine. ... View more

Thanks for the idea. Truthfully, this is the intention. However, the ArcGIS System is vast and rapidly evolving, and so are the various native platforms we support. This unfortunately means that we often have to make tough decisions on where to focus our time and effort. With that said, our goal is to make our customers successful and work on things that they see as valuable. If there are specific features that anyone sees as higher priority than others, I'd encourage you all to reach out to us on the forums, through account managers, and conferences, so we can make sure we are prioritizing the right work. Thanks, Lucas ... View more

The GeometryEditor is the next generation of sketching tools in the Maps SDK. While the GeometryEditor uses GraphicsOverlay to draw some of the map elements, that's an internal implementation detail and we don't plan on exposing raw access to those objects. There are numerous overlays and graphics at play, and actually modifying them to get a desirable output would be difficult. If there are specific additions or modifications you'd like added to the sketching experience, I'd highly recommend logging enhancements for those, as that will be the best avenue to improve the API. ... View more