Frameworks/Qt6 Porting Notes: Difference between revisions

Latest revision as of 17:20, 22 January 2022

In this page we aim to have a place to have a list of issues we face while porting/building the Frameworks to Qt6. Basically issues that aren't documented yet in https://doc.qt.io/qt-6/portingguide.html or https://doc.qt.io/qt-6/modulechanges.html

@@ Line 1: / Line 1: @@
-In this page we aim to have a place to have a list of issues we face while porting/building the Frameworks to Qt6.
+In this page we aim to have a place to have a list of issues we face while porting/building the Frameworks to Qt6. Basically issues that aren't documented yet in https://doc.qt.io/qt-6/portingguide.html or https://doc.qt.io/qt-6/modulechanges.html
-* Don't initialize a QVariant of QString with <code>QVariant(QString())</code>, instead use <code>QVariant()</code>
-** In Qt5 QVariant::isNull() returned true if the value stored in it was null, i.e. <code>QVariant(QString()).isNull()</code> would return true. In Qt6 however the behavior has been made more consistent, i.e. <code>QVariant::isNull()</code> returns true if this is a default constructed <code>QVariant</code> and false otherwise, it doesn't pertain to the underlying type stored in <code>QVariant</code>. See [https://invent.kde.org/frameworks/ki18n/-/commit/e548c4649961ffeaa0826717cabc28126330784d this] for more details