Latest Contributions by JamesBallard1

Hi @BBBAYRAM , Thanks for the info. I will bring this info to the Runtime team as a justification to reopen the Beta, but unfortunately I cannot promise anything. It is unlikely we can spin the project back up unless we hear from a few more users.

Hi @BBBAYRAM , Unfortunately we have closed this project and it never progressed out of the beta phase. I am interested to hear about your specific case and if this is something we can consider reopening the beta program for. I can say that the Beta did require full, Desktop-class OpenGL support and not OpenGL ES. Included with the Beta were some instructions on how to build a version of Qt for the target hardware that would target OpenGL, which is not the default for embedded devices. We had only tested on higher-end devices, such as the NVidia Jetson TX2 and Jetson Nano. To answer your question, no, the beta won't work on the i.MX8 unfortunately due to our OpenGL requirements.

‎12-16-2020

Hi @alphacoder , Is there any ArcGIS Runtime workflow you're trying to achieve with this? If not it's a bit off topic and more related to QML general programming. Generally speaking, whenever we've had to do image processing we use the QQuickImageProvider pattern, which does require a bit of C++ logic. I don't know if this directly applies to your use case, but I hope it is helpful. https://github.com/Esri/arcgis-runtime-samples-qt/blob/master/ArcGISRuntimeSDKQt_CppSamples/Maps/TakeScreenshot/MapImageProvider.h https://doc.qt.io/qt-5/qtquick-imageprovider-example.html https://doc.qt.io/qt-5/qquickimageprovider.html

‎11-19-2020

@JeremyRoberts2 , Unfortunately I do not know of any SDK or server changes you can make with 100.7 to work around that memory issue. We are working hard on Update 10 to get that out to you soon!

‎11-19-2020

@JeremyRoberts2 , I hear your concerns. I can tell you that we have some enhancements planned for the next release that should alleviate the issues related to the feature tiling requests getting queued up, resulting in worse performance. I am looking forward to getting the Update 10 release into your hands so both of these issues are resolved for you.

‎11-18-2020

Hi @JeremyRoberts2 , Thanks for reaching out the Qt team, and especially thank you very much for the excellent reproducer app. That was a big help in looking into the problem. I can reproduce the issue with 100.7 and 100.8, but not 100.9. Are you able to try the 100.9 release and see if the problem is still happening for you? Please let me know if 100.9 works for you.

‎10-29-2020

Hi Jan Tschada‌, No, unfortunately there is no guaranteed way to get the http service error from the Qt API. In some cases, this information will be part of the error object, and you can connect to that like follows: connect ( featureTable , & FeatureTable :: errorOccurred , this , [ ] ( const Error & error ) { qDebug ( ) << "FeatureTable error:" << error . message ( ) << error . additionalMessage ( ) ; } ) ; ‍ ‍ ‍ ‍ But however, it is not a guarantee that this information will be included with the error object. Let me know if this helps.

‎10-15-2020

Hi Fatma Akdemir‌, We do have some Widgets examples apps in our samples repo. I would encourage you to take a look at those. arcgis-runtime-samples-qt/ArcGISRuntimeSDKQt_CppSamples_Widgets at master · Esri/arcgis-runtime-samples-qt · GitHub Also if you check into the templates we provide with our SDK, one of them is a Qt Widgets template. After you run the post installer after SDK installation, our templates will be integrated into Qt Creator. The widgets one will be called "ArcGIS Runtime 100.9 Qt Widgets app", or whatever version you have installed. Here is some info about our templates. Develop your first map app—ArcGIS Runtime SDK for Qt | ArcGIS for Developers The template shows a different workflow than our samples by subclassing QMainWindow and calling setCentralWidget. That might be closer to the pattern you use now.

‎10-09-2020

Hi Norbert Thoden‌, I am familiar with parts of the stack trace, but we would need some more information to diagnose the problem. Do you know if this only happens at shutdown? It looks like __run_exit_handlers is getting invoked which is cleaning up some internal global statics we have, and that is aborting. But it is curious since the applications seems to be shutting down already. I saw this online c++ - Why does my application crash sometimes with a SIGSEGV when it gets closed? - Stack Overflow. This is a random guess, but is it possible the Runtime C++ API library is getting linked twice into the application? That library is a static library, libEsriRuntimeQt.a. The static in question is located in libEsriCommonQt.so, but it may be getting loaded/initialized twice if libEsriRuntimeQt.a is linked twice into the application somehow.

‎10-08-2020

Brian Keller‌ another option is to use the refreshInterval on the FeatureLayer. FeatureLayer QML Type | ArcGIS for Developers

Online Status	Offline
Date Last Visited	yesterday

My Ideas

Latest Contributions by JamesBallard1

Re: Running Developer Examples on i.MX8 with ArcGIS Embedded Linux

Re: Running Developer Examples on i.MX8 with ArcGIS Embedded Linux

Re: convert image or imageobject to binary in qml

Re: Memory consumption increases exponentially and crashes app on iOS.

Re: Memory consumption increases exponentially and crashes app on iOS.

Re: Memory consumption increases exponentially and crashes app on iOS.

Re: Getting the underlying web error when querying a feature layer?

Re: How to migrate from QGraphicsView to MapGraphicsView?

Re: abort at exit_handler

Re: Does cache expire in on interaction cache mode?