|
BLOG
|
As discussed in a previous blog, a critical step to take in preparing your apps for version 200 is to replace deprecated APIs with current APIs and contemporary code. This blog describes how to do this in QML. Because QML is an interpreted language, it does not currently have a compiler, linter, or IDE tools to help you easily identify deprecated API usage. As such, we’ve introduced a property on ArcGISRuntimeEnvironment named logDeprecatedWarnings. This property logs to the console whenever a deprecated class, property, method, or signal is used in your app. The log content contains the API name that is deprecated, as well as the file and line number in some circumstances. After identifying deprecated API usage, consult the API reference doc to find a suitable replacement and make appropriate changes to your code. Please note that these warnings are run-time warnings, not compile-time warnings. This means the warnings will be logged throughout the lifetime of running your apps. Thus, it is important to fully test your app to ensure all code paths are run. Some common potential pitfalls include: QML files or Components that are loaded with a QML Loader, StackView, or other similar pattern. The QML engine will not parse these files or components until they are loaded, so it is essential that your app testing loads all QML files and code. JavaScript code is not parsed by the QML engine when the file is loaded, but rather when the JavaScript code is run. For example, in this case the warning will be logged when the button is clicked. This property is enabled by default. It can be disabled by setting the property to false.
... View more
09-02-2022
12:45 PM
|
2
|
0
|
2714
|
|
BLOG
|
As discussed in a previous blog, a critical step to take in preparing your Qt apps for version 200 is to replace deprecated APIs with current APIs and contemporary code. This blog describes how to do this in C++. To simplify identifying deprecated APIs in C++, we’ve created a macro, QRT_DEPRECATED, that will raise compiler warnings for any deprecated usage in your app. The warnings will show up in Qt Creator like this: Qt Creator will also call out any usage in the code editor, making it very easy to identify where to make the changes. After identifying deprecated API usage, consult the API reference doc to find a suitable replacement and make appropriate changes to your code. The QRT_DEPRECATED macro is enabled by default, so you will see these warnings automatically.
... View more
09-02-2022
12:41 PM
|
2
|
0
|
5620
|
|
BLOG
|
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.
... View more
09-02-2022
12:35 PM
|
3
|
0
|
818
|
|
POST
|
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.
... View more
08-30-2022
07:24 AM
|
0
|
0
|
968
|
|
POST
|
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
... View more
08-26-2022
07:08 AM
|
1
|
0
|
6605
|
|
POST
|
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.
... View more
08-25-2022
06:35 AM
|
0
|
0
|
1662
|
|
POST
|
@Amitkhillan This is probably worth posting in the Android space as they may have a better idea what is going on
... View more
08-24-2022
08:20 AM
|
0
|
1
|
5067
|
|
POST
|
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
... View more
08-24-2022
08:18 AM
|
0
|
0
|
4955
|
|
POST
|
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
... View more
08-08-2022
07:56 AM
|
0
|
0
|
4976
|
|
POST
|
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.
... View more
08-01-2022
07:42 AM
|
0
|
0
|
5003
|
|
POST
|
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?
... View more
07-27-2022
08:34 AM
|
0
|
0
|
3309
|
|
POST
|
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
... View more
07-27-2022
07:22 AM
|
0
|
0
|
5028
|
|
POST
|
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
... View more
07-25-2022
07:32 AM
|
1
|
2
|
3328
|
|
POST
|
We don't have a client side API at the moment, so you'll need to set it in the web map.
... View more
06-21-2022
07:29 AM
|
0
|
1
|
2347
|
| Title | Kudos | Posted |
|---|---|---|
| 3 | 3 weeks ago | |
| 1 | 11-24-2025 10:45 AM | |
| 1 | 07-30-2025 08:26 AM | |
| 1 | 05-15-2025 07:35 AM | |
| 2 | 11-26-2024 01:27 PM |
| Online Status |
Offline
|
| Date Last Visited |
Wednesday
|