Latest Contributions by LucasDanzinger

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

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

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