Qt Safe Renderer 2.0 Release Note Impact Analysis

C

New Features and Runtime API Changes

This topic lists:

New Features in Qt Safe Renderer 2.0

Qt Safe Renderer 2.0 provides the following new features:

  • Rendering output verification for Qualcomm Snapdragon SA8155P. Display processor unit (DPU) CRC calculation is used for output verification. For more information, see Output Verification.
  • The fillColor feature provides a solid background color for Safe QML elements, ensuring visibility and readability by checking contrast against WCAG 2.1 guidelines. For more information, see Using fillColor Property.
  • MISRA-C Monitor. For more information, see Monitor: Verifying the Rendering Output.
  • Localization support. For more information, see Localizing Safety-Critical QML Types, Enabling Localization in Qt Safe Renderer project, and Localization example.
  • Touch support enabler. For more information, see the SafeTouch API documentation and FAQ How does Qt Safe Renderer support safety-critical touch input?.
  • The Z-order feature improves repainting of items by automatically refreshing overlapping UI elements. This replaces manual refreshing, making UI management easier.
  • QSafeEventSender module provides new API for sending safe events from external processes to the renderer process. It uses operating system specific event queues for safe inter-process communication.
  • Pre-built Qt Safe Renderer binaries built with Qt 5.15.12. Binaries are provided for the Qt Safe Renderer tools and plugins.

The following blog posts provide useful information about the new features in Qt Safe Renderer 2.0:

Qt Safe Renderer 2.0 Runtime API Changes

After the Qt Safe Renderer 1.2 release, the Qt Safe Renderer 2.0 Runtime API has changed as follows:

Summary: Change in QSafeAnimation API

See the C++ API documentation: SafeRenderer::QSafeAnimations.

Description:

A change has been made to the QSafeAnimation API in the software. The method count() has been renamed to countOfAnimations(). This change ensures that the name of the method is more descriptive and accurately reflects its purpose.

Impact:

This change will affect any code that relies on the QSafeAnimation API. Developers should update their code accordingly to avoid any compatibility issues with the latest version of the software.

Summary: Change in QSafeBitmapBuffer API

See the C++ API documentation: SafeRenderer::QSafeBitmapBuffer.

Description:

The SizeError enumeration value has been removed.

Impact:

This change will affect any code that relies on the QSafeBitmapBuffer API and specifically the BitmapExceptions enumeration. Developers should update their code accordingly to avoid any compatibility issues with the latest version of the software.

Summary: Change in QSafeBitmapResourceReader API

See the C++ API documentation: SafeRenderer::QSafeBitmapResourceReader.

Description:

The function loadBitmapFile has been renamed to loadBitmap.

Impact:

Developers should update their code accordingly to avoid any compatibility issues with the latest version of the software.

Summary: Change in QSafeByteArray API

See the C++ API documentation: SafeRenderer::QSafeByteArray.

Description:

Renamed the data() function to byteArrayData().

Impact:

Developers should update their code accordingly to avoid any compatibility issues with the latest version of the software.

Summary: Change in QSafeEventVisibility API

See the C++ API documentation: SafeRenderer::QSafeEventVisibility.

Description:

The id() method in the QSafeEventVisibility class has been renamed to itemId().

Impact:

Developers should update their code accordingly to avoid any compatibility issues with the latest version of the software.

Summary: Change in QSafeEventPosition API

See the C++ API documentation: SafeRenderer::QSafeEventPosition.

Description:

The method setId in class QSafeEventPosition has been renamed to setItemId.

The method id in class QSafeEventPosition has been renamed to itemId.

Impact:

Developers should update their code accordingly to avoid any compatibility issues with the latest version of the software.

Summary: Change in QSafeEventHeartbeat API

See the C++ API documentation: SafeRenderer::QSafeEventHeartbeat.

Description:

The method name setTimeout has been renamed to setHeartbeatTimeout.

The method name timeout has been renamed to heartbeatTimeout.

Impact:

Developers should update their code accordingly to avoid any compatibility issues with the latest version of the software.

Summary: Change in QSafeEventSetText API

See the C++ API documentation: SafeRenderer::QSafeEventSetText.

Description:

The method setId(const quint32 valueArg) has been renamed to setItemId(const quint32 valueArg).

The method quint32 id() const has been renamed to quint32 itemId() const.

Impact:

Developers should update their code accordingly to avoid any compatibility issues with the latest version of the software.

Summary: Change in QSafeEventSetColor API

See the C++ API documentation: SafeRenderer::QSafeEventSetColor.

Description:

The method setId has been renamed to setItemId.

The method id has been renamed to itemId.

The readFontData function has added an argument fontDataSize and the argument data has been renamed to fontData.

Impact:

Developers should update their code accordingly to avoid any compatibility issues with the latest version of the software.

Summary: Change in QSafeFontLoader API

See the C++ API documentation: SafeRenderer::QSafeFontLoader.

Description:

The name of the method getId has been renamed to getFontFileId, and the name of the method setId has been renamed to setFontFileId.

Impact:

Developers should update their code accordingly to avoid any compatibility issues with the latest version of the software.

Summary: Change in QSafeLayout API

See the C++ API documentation: SafeRenderer::QSafeLayout.

Description:

The virtual public member function stateLoader now returns a constant reference instead of a non-constant reference.

The virtual public member function textLayoutReader now returns a constant reference instead of a non-constant reference.

Impact:

All the changes made to the API are non-breaking and can be used by existing code with a recompile.

Summary: Change in QSafeLayoutFileReader API

See the C++ API documentation: SafeRenderer::QSafeLayoutFileReader.

Description:

The return type of the methods stateLoader and textLayoutReader has been changed from non-const to const.

Impact:

All the changes made to the API are non-breaking and can be used by existing code with a recompile.

Summary: Change in QSafeLayoutResourceReader API

See the C++ API documentation: SafeRenderer::QSafeLayoutResourceReader.

Description:

In QSafeLayoutResourceReader class, the return type of stateLoader() and textLayoutReader() functions has been changed from non-const to const.

Impact:

All the changes made to the API are non-breaking and can be used by existing code with a recompile.

Summary: Change in QSafeRenderer API

See the C++ API documentation: SafeRenderer::QSafeRenderer.

Description:

The return type of methods drawBitmap and clearBitmap has been changed from Rect to QSafeRect.

The second argument for the method clearBitmap has been added, with a default value of false. This argument specifies whether to use the global clear color or not.

The names of parameters in methods doDrawBitmap, doDrawCompressedBitmap, and doClearBitmap have been changed from id to itemId.

Impact:

Developers should update their code accordingly to avoid any compatibility issues with the latest version of the software.

Summary: Change in QSafeString API

See the C++ API documentation: SafeRenderer::QSafeString.

Description:

In the QSafeString class, the member function {data()} has been renamed to rawCString().

The member function len() has been renamed to length().

Impact:

Developers should update their code accordingly to avoid any compatibility issues with the latest version of the software.

Summary: Change in QStringSplitter API

See the C++ API documentation: SafeRenderer::QStringSplitter.

Description:

In the QStringSplitter class, the function next() has been renamed to nextSubString().

Impact:

Developers should update their code accordingly to avoid any compatibility issues with the latest version of the software.

Summary: Change in AbstractFrameBuffer API

See the C++ API documentation: SafeRenderer::AbstractFrameBuffer.

Description:

Rect class has been renamed to SafeRect. A new header file qsaferect.h has been added to the src/saferenderer directory.

In the AbstractFrameBuffer class, the method bits() has been renamed to framebufferData(). The method format() has been renamed to framebufferFormat().

Impact:

Developers should update their code accordingly to avoid any compatibility issues with the latest version of the software.

Summary: Change in AbstractWindow API

See the C++ API documentation: SafeRenderer::AbstractWindow.

Description:

The method render now takes an additional argument idArg, of type quint32, representing the window id.

Impact:

Developers should update their code accordingly to avoid any compatibility issues with the latest version of the software.

Summary: Change in StateManager API

See the C++ API documentation: SafeRenderer::StateManager.

Description:

The Value enum has been renamed to Visibility, with the values ValueOff and ValueOn being renamed to Hidden and Visible respectively.

changeVisibleState method now takes the Visibility enum instead of the {Value} enum.

Impact:

Developers should update their code accordingly to avoid any compatibility issues with the latest version of the software.

Qt Safe Renderer 2.0 Release Note Impact Analysis

Available under certain Qt licenses.
Find out more.