Latest Contributions by LucasDanzinger

‎09-02-2022

Later this year, the ArcGIS Runtime team will release version 200.0 of ArcGIS Runtime SDK for Qt, which will fully support Qt 6. Version 200 will be a significant update to the produce, as Qt 6 will enable us to support newer platforms, hardware, rendering APIs, and compilers (see our Qt 6 announcement blog post for more details). As you may know, the move from Qt 5 to Qt 6 contains breaking changes that must be addressed to compile your app with Qt 6. The Qt Company has created a migration guide to assist you in porting your apps. The first two steps are critically important: Upgrade your app to the latest version of Qt 5.15. Remove and replace deprecated APIs in your apps. Where possible, Qt has attempted to deprecate APIs that will be removed at Qt 6, which gives developers an opportunity to remove their usage from apps before moving to Qt 6. To make this migration as seamless as possible, Esri is following The Qt Company’s plan, and has deprecated several classes, properties, and methods in version 100.15 and prior. Our plan is to remove these APIs from version 200. In lockstep with The Qt Company, Esri recommends that you upgrade your apps to the latest version of Qt 5.15 and ArcGIS Runtime SDK version 100.15. After upgrading, we recommend removing deprecated API usage in your apps. Doing these things ahead of time will make your migration effort much simpler once version 200 is available. The next blogs in this series cover how to find and change deprecated APIs in your code. Because the workflow varies greatly between the C++ and QML APIs, there are two different posts. You only need to review the post for the API that you use.

‎08-30-2022

Hello, we don't have a specific sample or tutorial for Search/Geocode with Qt Widgets. The actual Runtime API usage will be the exact same as the tutorial (using LocatorTask to run a geocode). For the UI, you could use a QLineEdit - https://doc.qt.io/qt-5/qlineedit.html Here is a basic "Display a map" sample that will show you a very basic workflow of using our API in Widgets. The only real difference is that you will use a MapGraphicsView instead of a MapQuickView.

‎08-26-2022

The directory with the mmap and various other files is an "unpacked" mobile map package. The constructor to MobileMapPackage takes either the path to a file with .mmpk extension or to the directory of an unpacked mobile map package. https://developers.arcgis.com/qt/cpp/api-reference/esri-arcgisruntime-mobilemappackage.html#MobileMapPackage

‎08-25-2022

The sample itself deletes the mmpk on exit by use QTemporaryDir. If you modify it to output to a different non-temp location, it won't be deleted.

‎08-24-2022

@Amitkhillan This is probably worth posting in the Android space as they may have a better idea what is going on

‎08-24-2022

You can create a MMPK in Pro. You can also generate one on-demand from a web map using our OfflineMapTask. This sample demonstrates how to do this https://github.com/Esri/arcgis-runtime-samples-qt/tree/main/ArcGISRuntimeSDKQt_CppSamples/Maps/GenerateOfflineMap

‎08-08-2022

The data is available for download on ArcGIS Online. Details are in the sample readme - https://github.com/Esri/arcgis-runtime-samples-qt/tree/main/ArcGISRuntimeSDKQt_CppSamples/Maps/OpenMobileMap_MapPackage#offline-data

‎08-01-2022

Yes, it's definitely possible. The actual C++ back end code will be nearly identical. You can disregard the QML portions of the samples, as those are just the UI - you'd use Qt Widgets for your UI instead.

‎07-27-2022

CalloutData contains all of the information about where to display the view (screen point) and what to display in the view (title, detail, image, etc). This will be applicable whether using Qt Quick and Qt Widgets. The piece that is missing for Widgets is the actual view. In Qt Quick, we use QML Shapes to draw the actual view. We used to use a QML Canvas before Shapes was introduced. For Widgets, I don't have any specific recommendations at this point, as we haven't prototyped anything yet. Perhaps you could use QPainter or something along those lines?

‎07-27-2022

We don't have specific Widgets samples for these, but we have C++ Qt Quick samples. The actual code to perform these is nearly identical (the only difference between Widgets and Qt Quick is MapQuickView and MapGraphicsView class). Offline map on demand - https://github.com/Esri/arcgis-runtime-samples-qt/tree/main/ArcGISRuntimeSDKQt_CppSamples/Maps/GenerateOfflineMap Preplanned offline map - https://github.com/Esri/arcgis-runtime-samples-qt/tree/main/ArcGISRuntimeSDKQt_CppSamples/Maps/DownloadPreplannedMap Load mobile map package - https://github.com/Esri/arcgis-runtime-samples-qt/tree/main/ArcGISRuntimeSDKQt_CppSamples/Maps/OpenMobileMap_MapPackage Get coordinates from mouse click - connect to the mouse clicked signal (https://developers.arcgis.com/qt/cpp/api-reference/esri-arcgisruntime-mapgraphicsview.html#mouseClicked) and then call screenToLocation to convert the screen point to map point https://developers.arcgis.com/qt/cpp/api-reference/esri-arcgisruntime-mapview.html#screenToLocation

‎07-25-2022

It is still not available yet.

‎07-25-2022

Yes, this is still the case. I think you have a few options: * Build your own Callout in Widgets. This could use the CalloutData class still to determine where to draw the callout and what it should display. https://developers.arcgis.com/qt/cpp/api-reference/esri-arcgisruntime-calloutdata.html * Use a TextSymbol to display text at a given location https://developers.arcgis.com/qt/cpp/api-reference/esri-arcgisruntime-textsymbol.html

‎06-21-2022

We don't have a client side API at the moment, so you'll need to set it in the web map.

‎05-23-2022

Hello, Sounds like you were able to get Linux and Windows working? For Mac, it gets a little bit trickier. Have you run the macdeployqt script (described here https://doc.qt.io/qt-5/macos-deployment.html)? Generally to build our sample viewers for mac, our workflow is: build the app, run macdeployqt script, copy in the remaining dylibs (EsriCommonQt, runtimecore), and run `install_name_tool -change` on them/the app executable so the exe looks in the app bundle for the libs and not elsewhere. This step is necessary because the dylibs contain references to the library dependencies with specific paths - you can double check the references with `otool -L`. Hopefully this gets you on the right track

‎05-17-2022

The static libraries will be compiled into your application, and the libEsriCommonQt.so and libruntimecore.so shared libraries need to be in your application's path. The easiest way to do this is to place the shared libraries that your app depends on next to the executable. I'd recommend referencing the sample applications we have as a starting point. You can inspect the libraries there and replicate the structure/required libs in your app: https://www.arcgis.com/home/search.html?t=content&q=tags%3A%22CppSampleViewer%22

Online Status	Offline
Date Last Visited	4 weeks ago

My Ideas

Latest Contributions by LucasDanzinger

Prepare your Qt apps for migrating to 200

Re: How add search address bar for QT Widgets app

Re: Qt C++ Widgets Samples

Re: Qt C++ Widgets Samples

Re: Loading .TPK File instead of Online Basemap

Re: Qt C++ Widgets Samples

Re: Qt C++ Widgets Samples

Re: Qt C++ Widgets Samples

Re: Callout example in ArcGIS Qt

Re: Qt C++ Widgets Samples

Re: gradient color polygon

Re: Callout example in ArcGIS Qt

Re: How to render a feature layer using multiple fields in the query condition?

Re: cmake/cpack shared libraries

Re: cmake/cpack shared libraries

Re: Possible memory leak with Dictionary Renderer ...

Logging into the future: Introducing the Next Gene...

Re: Ubuntu 24.04 Qt Version 6.4.2 is not compatibl...

Re: Windows Deployment

Re: Converting image into .tpk format