Transition from Qt 4.x to Qt5

From Qt Wiki
Revision as of 23:03, 27 April 2024 by Budi (talk | contribs) (smplify)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

En Ar Bg De El Es Fa Fi Fr Hi Hu It Ja Kn Ko Ms Nl Pl Pt Ru Sq Th Tr Uk Zh

The transition from Qt 4.x to Qt 5 is not expected to be significant. However, the "modularization" of the Qt code base requires some amount of changes to project configuration, such as use of "headers", and configuration of project build settings (such as changes to the *.pro files).

QtWidgets as a Separate Module

example compile time errors

error: QMainWindow: No such file or directory
error: QToolButton: No such file or directory
error: QWidget: No such file or directory


Add this in every *.pro file in your project:

QT += widgets

Change all instances of

#include <QtGui>


#include <QtWidgets>

The code should work now, though sometimes you may require to be more explicit:

#include <QtWidgets/QToolButton>

QtWebKitWidgets is also a separate module:

example compile time errors

error: invalid use of incomplete type 'class QWebFrame'
error: forward declaration of 'class QWebFrame'


Add this in your *.pro file:

QT += webkitwidgets

Note: when you have QT += webkitwidgets you don't need QT += widgets

In addition, replace all instances of

#include <QtWebKit>


#include <QtWebKitWidgets>

You can try this by porting a WYSISWYG html editor from Qt 4 to Qt 5.

QPrinter Doesn't Work

If your code has the following lines:

#include <QPrinter>
#include <QPrintDialog>

add the following to your project file:

QT += printsupport

Again, sometimes it may not work and you would need to be explicit:

#include <QtPrintSupport/QPrinter>
#include <QtPrintSupport/QPrintDialog>

toAscii() and fromAscii() Methods are deprecated

Replace all instances of




For example, given the Qt 4 code

QByteArray configfileti = TMP_Config.toAscii();

you would change to

QByteArray configfileti = TMP_Config.toLatin1();

QCoreApplication::UnicodeUTF8 is deprecated

This enum type used to define the 8-bit encoding of character string arguments to translate(). This enum is now obsolete and UTF-8 will be used in all cases. So remove all instances of QCoreApplication::UnicodeUTF8. For example:

Href_Gui->setWindowTitle(QApplication::translate("Href_Gui", "Url / www", 0, QApplication::UnicodeUTF8));
label->setText(QApplication::translate("Href_Gui", "Text:", 0, QApplication::UnicodeUTF8));
label_2->setText(QApplication::translate("Href_Gui", "Url:", 0, QApplication::UnicodeUTF8));
label_3->setText(QApplication::translate("Href_Gui", "Target / Name:", 0, QApplication::UnicodeUTF8));


Href_Gui->setWindowTitle(QApplication::translate("Href_Gui", "Url / www", 0));
label->setText(QApplication::translate("Href_Gui", "Text:", 0));
label_2->setText(QApplication::translate("Href_Gui", "Url:", 0));
label_3->setText(QApplication::translate("Href_Gui", "Target / Name:", 0));

QWorkspace is deprecated

This class is obsolete and was replaced by the QMdiArea class in Qt 4.3. In Qt 5 QWorkspace has been removed. The new class has a similar API to QWorkspace and porting it only involved changing the names of a few methods, signals, and slots.


#include <QWorkspace>


#include <QMdiArea>

QDrag Problems

Apps that have drop and drag functionality will need some tweaking. A line such as

QDrag *drag = new QDrag(event->widget());

in Qt 5 will generate the error

error: no matching function for call to 'QDrag::QDrag(QWidget*)'

To fix this add among the includes:

#include <QWidget>

qFindChildren is deprecated

An error will pop of this fashion:

error: 'qFindChildren' was not declared in this scope

To solve this you replace qFindChildren with findChildren, for example in

toString(const QObject* obj, int indentLevel) const {
 /* Query over QObjects */
 if (m_children) {
 QList<QObject*> childlist = qFindChildren<QObject*>(obj, QString());


QList<QObject*> childlist = qFindChildren<QObject*>(obj, QString());


QList<QObject*> childlist = obj->findChildren<QObject*>(QString());


qInstallMsgHandler is deprecated

The 4.8 function qInstallMsgHandler has been replaced with qInstallMessageHandler. The functions are similar, but the function signature of the `handler` has also changed, adding a very useful QMessageLogContext and replacing the char array with a QString reference.

Your compiler will complain

error: 'qInstallMsgHandler': identifier not found

so replace

void myhandler(QtMsgType type, const char* msg) {
    switch (type) {
    case QtDebugMsg:
        fprintf(stderr, "Debug: %s\n", msg);
    case QtWarningMsg:
        fprintf(stderr, "Warning: %s\n", msg);
    case QtCriticalMsg:
        fprintf(stderr, "Critical: %s\n", msg);
    case QtFatalMsg:
        fprintf(stderr, "Fatal: %s\n", msg);

int main(int argc, char** argv) {
    QApplication app(argc, argv);
    return app.exec();


void myhandler(QtMsgType type, const QMessageLogContext& context, const QString& msg) { //<-- new signature! added context!
    QByteArray localMsg(msg.toLocal8Bit());       //<-- not a char* any more!
    switch (type) {
    case QtDebugMsg:
        fprintf(stderr, "Debug: %s (%s:%u, %s)\n",    localMsg.constData(), context.file, context.line, context.function);
    case QtInfoMsg:
        fprintf(stderr, "Info: %s (%s:%u, %s)\n",     localMsg.constData(), context.file, context.line, context.function);
    case QtWarningMsg:
        fprintf(stderr, "Warning: %s (%s:%u, %s)\n",  localMsg.constData(), context.file, context.line, context.function);
    case QtCriticalMsg:
        fprintf(stderr, "Critical: %s (%s:%u, %s)\n", localMsg.constData(), context.file, context.line, context.function);
    case QtFatalMsg:
        fprintf(stderr, "Fatal: %s (%s:%u, %s)\n",    localMsg.constData(), context.file, context.line, context.function);
        break;                                   //<-- Qt example doesn't abort() any more with fatal error

int main(int argc, char** argv) {
    qInstallMessageHandler(myhandler);          //<-- new function
    QApplication app(argc, argv);
    return app.exec();

qVariantValue is deprecated

Your compiler will say

error: 'qVariantValue' was not declared in this scope

This function is equivalent to QVariant::value<T>(value). Therefore if given a QVariant val rewrite the line

QTime t = qVariantValue<QTime>(val);


QTime t = val.value<QTime>();

This QTime enclosed in the angled brackets lets the compiler know what QVariant will return. However, if the variable is not a QVariable the type enclosed in the angled brackets should not be used(doing so will result in a vague compile time error). So given that m_color is of type QColor you will rewrite

s.setValue("color/favorite", qVariantValue<QColor>(m_color));


s.setValue("color/favorite", m_color.value());


qVariantCanConvert is deprecated





Qt::escape is deprecated

error: 'escape' is not a member of 'Qt'

So you would change the following block:

if (result == QString())
    result = Qt::escape(val.toString());
    result = Qt::escape(result);
return result;


if (result == QString())
    result = QString(val.toString()).toHtmlEscaped();
    result = QString(result).toHtmlEscaped();
return result;

this procedure can be automated by a porting tool from KDAB.

QDesktopServices::storageLocation deprecated

error: 'storageLocation' is not a member of 'QDesktopServices'
error: 'DataLocation' is not a member of 'QDesktopServices'

Use QStandardPaths::StandardLocation:

QString path = s.value("db.path", QDesktopServices::storageLocation(QDesktopServices::DataLocation)).toString();


QString path = s.value("db.path", QStandardPaths::standardLocations(QStandardPaths::DataLocation)).toString();


CONFIG+=qtestlib is deprecated

If you have the above line in your project file the compiler will warn you in the compile window, nonetheless the code will still run as usual:

Project WARNING: CONFIG+=qtestlib is deprecated. Use QT+=testlib instead.

QWeakPointer quirks

A code block like

quint64 decodedPointer = line.toULongLong();
MetaData* md = reinterpret_cast<MetaData*>(decodedPointer);
QWeakPointer<MetaData> wp(md);

results in

error: no matching function for call to 'QWeakPointer<MetaData>::QWeakPointer(MetaData*&)'

To fix this add to the project file:



QtConcurrent Library is Missing?

C:\Qt\5.0.2\5.0.2\mingw47_32\include\QtConcurrent\qtconcurrentthreadengine.h:133: error: undefined reference to 

In Qt 4, QtConcurrent was part of QtCore, so there was no need to include specific headers. This is no longer the case with Qt 5. If your source code has lines like

m_current = QtConcurrent::blockingMappedReduced(slices, functor, stitchReduce, QtConcurrent::UnorderedReduce );

You will need to include the header:

#include <QtConcurrent/QtConcurrent>

and add the following line to your project file:

QT+= concurrent

Fixing #include<> Headers

A Perl script "" exists in qtbase/bin/. that should be run on source code using Qt that corrects the #include<> directives for Qt components to also consider the module name.

Plugin loading

The Q_EXPORT_PLUGIN,Q_EXPORT_PLUGIN2 macros have been deprecated in favor of the new Q_PLUGIN_METADATA macro. The advantage of the new system is that it allows Qt to query the metadata for the plugin without actually dlopen'ing it. This greatly improves performance and reliability of the plugin system.

The new Q_PLUGIN_METADATA macro is included next to the Q_OBJECT macro in the QObject derived class that is returned when loading the plugin. It contains the plugins IID and a filename pointing to a json file containing the metadata for the plugin. The json file is compiled into the plugin and does not need to be installed.

An example on how to change your plugins can be found by looking at the patch that changes the Gif image format plugin, see

Deploying to systems without C++11

When Qt is built from source code on a system with C++11 installed, the Qt libraries/frameworks are linked against the system's C++11 library (libc). This means that the Qt libraries/frameworks are not deployable to systems without C++11 installed (such as out-of-the-box Mac OS X 10.6). To be able to deploy to systems that only support the older C++ standard (libstdc++), build Qt from source code with the -no-c++11 configure option.

QTimer is no longer accurate to the millisecond by default

QTimer has now 3 accuracy types, with a new default behaviour:

  • The new default type is Qt::CoarseTimer which, to reduce power/CPU consumption, allow 5% difference between requested time and actual one, and even allow the timer to fire before the requested time.
  • The former one is Qt::PreciseTimer (to the millisecond, never before the requested time).
  • A third one is Qt::VeryCoarseTimer and allow a 1 second difference

QUrl addQueryItem moved to QUrlQuery

If you have:

QUrl url;
// …
url.addQueryItem(key, value);

You will want to change it to

QUrl url;
QUrlQuery urlQuery(url);        //initialize with url to append to existing query, if present
// …
urlQuery.addQueryItem(key, value);


The same applies to the QUrl::getQueryItem() methods. They have been moved to QUrlQuery.

QAbstractItemModel changes

void reset()
void setRoleNames(const QHash<int, QByteArray> & roleNames)

both have changed and are now obsolete.

See Obsolete Members for QAbstractItemModel

QHeaderView changes


void QHeaderView::setSectionResizeMode(QHeaderView::ResizeMode mode)

instead of

void QHeaderView::setResizeMode(ResizeMode mode)

The latter has been removed.

Recommended Reading