Latest Contributions by JamesBallard1

@imbachb thanks for reporting this and sharing the code snippets. That helps make things easier for us to reproduce. We will investigate soon and let you know what we find. ... View more

@imbachb thanks for reaching out. We are going to have a think about whether we should go through with deprecating the 'Graphic::geometryChanged' signal. We took a broader look at all our GeoElement classes, and found some cases where that signal would not be emitted consistently. We are not confident that Graphic was in the category of classes that was ever incorrect or not. For now I can tell you that we simply emitted the signal any time Graphic::setGeometry was called, so you could update your logic to do the same or similar workflow. If that wouldn't work, please let me know so we can discuss within the team. ... View more

@KyleCzech thanks for the additional info. In that case, here are the things I recommend checking. Possible permissions issues. Some of our internal tests ran into early problems with permissions related to needing to have admin access to run our new configure powershell script. There was an internal MSVC 2022 update, but we may have missed updating our system requirements with the new version. I'd check that you have a recent version of MSVC 2022. Is it possible EsriCommonQt.dll and runtimecore.dll are being loaded from the 200.7 version or some mix of that? Visual Studio or Qt Creator can give you insights into which dlls are being loaded, and that might give some clues to the problem. Let us know how it goes. ... View more

Hi @KyleCzech. We do not guarantee ABI stability between versions like Qt does. You will need to recompile the app with the version you're using. One of our libraries is a static library, which requires recompiling. It's not clear, but it sounds like you've just dropped in the updated 200.8 dlls with your app and didn't recompile. Can you please try building your app with 200.8 and see if that helps?   ... View more

@FatmaAkdemir unfortunately no, no plans for setVisible or hide functionality. That would be similar to a display filter, and no immediate plans for that at the moment. ... View more

@FatmaAkdemir we recommend you check for errors in case anything goes wrong.  See the "Handling Errors" section here: https://developers.arcgis.com/qt/cpp/api-reference/working-with-qfuture.html https://developers.arcgis.com/qt/cpp/api-reference/esri-arcgisruntime-errorexception.html  All tasks can fail, so it is best to recognize when and if that happens so your code can recover (or ignore) accordingly. For example if you pass an invalid ID (doesn't exist, for example), then I assume the task will fail with an error indicating that's what happened. ... View more

@FatmaAkdemir I checked with our experts in this area, and it doesn't appear possible to do what you're asking about, unfortunately. It might be possible to use a DictionaryRenderer with a custom dictionary style to parse out the category from the field on-the-fly and return different symbols based on that, but I can't say for certain that would work, and it would be a major reworking of how your data is structured to prototype it. ... View more

@FatmaAkdemir  Currently only the track id field is supported on track lines with attribute renderers like unique value renderers. Also take a look at the attribute values... Possibly the label field is where the field name should be (like "Cat 11" with a value of "Cat 11").  If the track id was say, "Category" and the value was "Cat 11", then I would expect something like  UniqueValue("Category", "Category", QVariantList() << "Cat 11", new SimpleLineSymbol(SimpleLineSymbolStyle::Solid, QColor(Qt::darkYellow), 2.0, this), this);   to work.   ... View more

@FatmaAkdemir unfortunately there is no clean way to do this with DynamicEntityDataSource itself as there is with ArcGISStreamService. Something that is a possible workaround could be something along these lines. Before I even mention it, I need to be clear that this is not perfect, and there will be difficulties getting it right. At best this would only give you the ability to present a frozen snapshot of the data matching your filter criteria and it wouldn't support the live data streaming in. You could perform a query (via https://developers.arcgis.com/qt/cpp/api-reference/esri-arcgisruntime-dynamicentitydatasource.html#queryDynamicEntitiesAsync) and then from those results you could create temporary graphics from each entity's attributes and geometry. Then you can hide the DynamicEntityLayer and show your graphics. But again, this is just a snapshot and wouldn't support any additional data streaming in without extra plumbing to keep track of everything being added and constantly updating the graphics. Track rendering would also be lost, so there are major drawbacks to this approach, but it is something if you need to visualize which entities currently meet some filter criteria. ... View more

Thanks for the clarification, I will check with our team on this and get back to you. ... View more

Hi @FatmaAkdemir . We have some examples of custom dynamic entity data sources, take and look and let us know if that helps. https://github.com/Esri/dynamic-situational-awareness-qt/blob/b22f92be4dc4916f2c6f1d95d64fe7cda275861a/Shared/messages/MessageFeed.h#L40  https://github.com/Esri/arcgis-maps-sdk-samples-qt/tree/main/CppSamples/Layers/AddCustomDynamicEntityDataSource  I think if you want to match the functionality of ArcGISStreamServiceFilter, you could apply any filter when you process the data and choose whether or not to process it at all, for example here you can filter on any criteria and then simply not call addObservation. https://github.com/Esri/arcgis-maps-sdk-samples-qt/blob/main/CppSamples/Layers/AddCustomDynamicEntityDataSource/CustomDataSource.cpp#L104   ... View more