Latest Contributions by JamesBallard1

@TASL_Virendra , I hope the workaround was successful for you. We have fixed this bug in the next release of Runtime, 100.12. This will be out before the end of 2021. ... View more

@OSINT_ENGINEER  Are you able to share your CPU details? AVX aside, it doesn't support SSE3 or SSSE3 which were introduced in 2004 and 2006. I do believe our library will contain both SSE3 and SSSE3 instructions so you'd need a more modern CPU to support those. I will look into AVX and see if we have this requirement now for 100.11. I used the ArcGIS Runtime 100.9 with Win10 and VS C++ on this machine before and it worked like a charm. That is using the visual studio compilers which may have different cpu instruction sets enabled.   ... View more

Hi @EkkaratPrasongsap , I reached out to Qt Support regarding this issue and got a reply. It turns out that the version of Qt that we build against defines this symbol (as you know), but different versions of Qt either provided by package managers or built locally with different compilers do not define this symbol (as you're seeing when you build it locally). This puts us in a difficult situation since we are building against the "official" qt release binaries provided by The Qt Company, but developers like yourself aren't able to use our software. My recommendation for now is to use the binaries provided directly from The Qt Company via their installer if you can. That should alleviate the problem for you. Short of that, you could include a source file that implements this symbol (annotated to resolve the error) in your code, but that is a last resort and I would not recommend it if you can avoid it.   ... View more

@OSINT_ENGINEER  I ran some tests on a fresh Ubuntu 20.04 install on our end. In addition to the packages you mentioned I also added mesa-common-dev for libGL (I couldn't build our apps without that). Once all those were in place, I was able to build and run both the Qt Widgets and Qt Quick samples with no crashes. I am using Runtime 100.11 and Qt 5.15.2 downloaded from the Qt Company's online installer. ... View more

@OSINT_ENGINEER  Is it possible to get some debug symbols for the libruntimecore.so? Yes, but that request has to go through Esri support. We are preparing that soon on the team so it should be ready shortly. I will do some tests on Ubuntu 20.04 to double check our previous testing efforts. In the meantime when you run your tests can you set LD_DEBUG to bindings? You will see every library that is loaded. LD_DEBUG=bindings (on the command line)  If anything is not found, I think the LD_DEBUG output might help spot the problem. Also, you'd be able to spot if anything is being loaded from an older version of Qt or anything else that seems off. ... View more

Hi @OSINT_ENGINEER , We have tested on Ubuntu 20.04 LTS and not seen this issue before. If you setup the environment and runtime ldd -r on libruntimecore.so, are there any unresolved symbols? Another thing to check would be to see if there is a secondary install of Qt installed on the system that's getting picked up first in the LD_LIBRARY_PATH vs your build path. We've see strange things like this where Qt 5.13 (for example) is installed on the system but we're building with Qt 5.15 and Qt 5.13 is loaded at runtime. In your systeminfo.txt file, it shows Qt 5.12.8 libraries, and your shadow build directory is displaying Qt 5.15.2. I would start there and see if a different version of Qt is getting picked up at runtime. ... View more

Hi @FatmaAkdemir .   That is likely a feature that would be in our toolkit but we don't have any such toolkit component right now. I assume you know how to get the distance with the GeometryEngine, but are looking for a UI element to display on screen representing a ruler, is that correct? ... View more

Hi @MKa , This community more for specific questions regarding the Runtime SDKs. This question is more along the lines of Survey123 or AppStudio since it's very specific to the workings of Survey123 and not any specific Runtime APIs. Would you consider posting this in either of these communities? We don't have the expertise on the Runtime SDK for Qt team to help with something this specific about Survey123. https://community.esri.com/t5/arcgis-survey123-questions/bd-p/arcgis-survey123-questions  https://community.esri.com/t5/arcgis-appstudio-questions/bd-p/arcgis-appstudio-questions   Good luck! The Survey123 team is very active and will be able to assist. I would recommend the Survey123 community first. ... View more

Hi @EkkaratPrasongsap , We have other reports of this as well. From what we can tell, this happens when you obtain Qt from a Linux distribution rather than directly from the Qt Company. There are more details here: https://community.esri.com/t5/arcgis-runtime-sdk-for-qt/undefined-reference-to-operator-delete-void-unsigned-long-qt-5/td-p/238562 That thread also has a proposed workaround from @NorbertThoden that worked for him and another user. We're not sure why one version libQt5Core.so.5 would implement this method and a different libQt5Core.so.5 would not. operator delete(void*, unsigned long)@Qt_5   We build the ArcGIS Runtime SDK for Qt against a version of Qt we download directly from The Qt Company. If that is an option for you, that might be the path of least resistance. ... View more

Thanks @JeanLonneux for the update. If you are still seeing issues with 100.11 do let us know so we can look into it. For example, if you run your unaltered app with 100.10 vs 100.11 and you are seeing 100.11 use more memory and continuously rise, please let us know. Thanks. ... View more

Hi @JeanLonneux , I've debugged the problem for a while on our end and I can see that there is definitely a new issue with 100.11. I have a potential workaround you can try for now. If you're able, can you test to see if you can reproduce the problem on your end with 100.10? I suspect you won't be able to, but I want to confirm I am narrowing in on the same thing you're seeing. I modified your test app locally to create thousands more graphics, and much faster in order to exacerbate the problem. In my local test this is enough to trigger a leak: void Process::dataIn(QString msg) { for (int i = 0; i < 1000; i++) { // just create/delete a bunch of graphics std::make_unique<Graphic>(); } }   As a workaround with 100.11, can you try creating the Graphic objects in either the main thread, or any thread that will have a longer-lived event loop? We have some internal data structures that only get cleaned up when some internal objects emit the destroyed signal. As a quick test, if I shift that code to this part of the test app, the problem goes away entirely: void Controller::process() { for (int i = 0; i < 1000; i++) { std::make_unique<Graphic>(); } // Create Thread to draw symbols QThread *thread = new QThread(this); // Create worker to draw Process *worker = new Process(my_Map); worker->moveToThread(thread); connect(this, SIGNAL(callProcess(QString)), worker, SLOT(dataIn(QString))); connect(thread, &QThread::finished, worker, &Process::deleteLater); thread->start(); // callProcess("test"); }   The difference is that the "process" function happens on the main thread. ... View more

Hi @MarkHolm , No, there is no way to know if a given feature is cached vs from the service. It would be difficult to have confidence in that anyway, since features displayed on the map could fall out of sync with the service at any time. I assume you're working with a ServiceFeatureTable, so I would recommend you look into the different feature request modes available. https://developers.arcgis.com/qt/qml/api-reference/enums-featurerequestmode.html  In your situation if it's critical to always have the latest data, Enums.FeatureRequestModeOnInteractionNoCache might be the best option since it will always request the latest features from the service. It does have performance implications since it needs to query the service constantly. If you view the class documentation for ServiceFeatureTable there is more information about how these options work. Also, you may be able to use populateFromService with clearCache=true to refresh all features in conjunction with Enums.FeatureRequestModeOnInteractionCache to get better performance overall. https://developers.arcgis.com/qt/qml/api-reference/qml-esri-arcgisruntime-servicefeaturetable.html#populateFromService-method   ... View more