Thank you for your reply. Wile the suggested solution might work, it feels a little like taking one step back, as the setup of layers and renderers are no longer part of the view, as partially intended by the new design. In addition, it appears like I still won't be able to leverage the clustering, or other filtering mechanism as the Graphics property is read only (referring Point Clustering Tips and Tricks from DevSummit 2016).
Our application displays one or more maps with Fleet tracking to the user, where the user can see the same information from different scales and extents, in different maps, at the same time. Each map contains a number of different layers with the same graphics, and most of them are dynamic in nature, with varying degree of movement. In the old ArcGIS Runtime SDK for WPF we ended up cloning all graphics, and keeping them up to date, which required a lot of unecessary code, however, we needed this as Graphic could only be added to one layer/map. Before quartz, this was not an issue, as I could bind the same collection to GraphicsLayer. There was one limitation that I had just recently figured out, was to show/hide sub-types of a layer (i.e. show vehicles, but hide helicopters; within the same layer), which was through similar approach as the point cluster sample. In the quartz release, it appears I have now lost the ways of doing the things that I need to do, at least without making the code base a lot bigger. At least with the current requirements.
Is there any chance the GraphicsSource property will be introduced in the next version of the SDK?
These are my wishes
- Bindable collections for GraphicsSource
- Being able to update graphics/attributes without having to switch threads; i.e make it happen in the background/rendering pipeline, where the appropriate dispatcher is available. However, I understand this limitation may be to make the rendering pipeline as fast as possible.
Do you have a link to a roadmap for the product?