That lead to me looking at the documentation for identifyGraphicsOverlayAsync ( https://developers.arcgis.com/qt/cpp/api-reference/esri-arcgisruntime-geoview.html#identifyGraphicsO... ) , The documentation does not seem to have any warnings to developers that they need to manage the memory in the QFuture functor. Should it have the little "See also Returned QObjects Parenting." link to remind developers like the old identifyGraphicsOverlaysCompleted does?
How could this app be improved with:
unit tests on the setters and getters logic
integration tests to see how the interaction with the classes in the app with a running Esri map
code coverage to see how much of the code is exercised by tests
a continuous integration setup?
Mainly because in my day job we have our map app working and have "seen the light" on the usefulness of those processes. But we have done it our way and I would like to see someone else's pattern for these processes.
