Qt5 porting tips/findings
-
I found another previously-undocumented change:
- QPen now has a default width of 1 instead of 0, so it is no longer cosmetic by default.
Anyway, most of the changes listed in this thread have are now in the official documentation. Thanks for sharing them here, altera_2011 and DerManu. See https://codereview.qt-project.org/56853
The patch has been accepted, and the documentation should appear in http://doc-snapshot.qt-project.org/qt5-stable/qtdoc/sourcebreaks.html soon.
Some notes:
- The changes to QTcpServer, QPointer and PostScript support were documented before my patch -- you can already read them in the snapshot
- Did QImage::load() work with sequential devices in Qt 4? If it did, then it's a regression bug, not a porting issue (please report to http://bugreports.qt-project.org/ )
- The conflict with windows.h is a library conflict, not a porting issue (might still be worth reporting, to see if we can implement an easy workaround in Qt)
- I could not reproduce the QFrame change -- I created a blank QFrame in Windows 8 with Qt 5.1 beta 1, and it was grey, not white
-
"QTcpServer::incomingConnection(qintptr handle)"
You just made my night, spent an hour looking wondering if I was insane :)
-
Another good one is QString::toASCI() has been depreciated, use QString::toLatin1()
-
Yep. that change is incredibly sneaky since it doesn't throw any error. Glad it saved you some time
-
Hi altera_2011.
I'm going to port my Qt 4 application to Qt 5. I have a big Visual Studio (2008) solution with a lot of projects because I have a lot of qt plugins.
My doubt is about the Visual Studio project (and not about the application source code).
I know that with Qt 5 some modules have changed, so I would like to know what's the best procedure to port the Visual Studio project.
I don't know if I can use my old project and change the project settings, or if I must create a new project...Thanks
-
puffosauro, I wish I had good advice for you but we use qmake and QtCreator instead of the VS2010 IDE. So in that respect the change to Qt 5 was a non-event as qmake took care of the changes.
How did you create the visual studio projects?
-
I have used the Visual Studio Addin to create the VS projects and also to add Qt classes etc... so I don't have a .pro file.
-
I'm sorry I'm not familiar with the VS addin. Maybe someone else can give some suggestions.
-
[quote author="puffosauro" date="1389276361"]I have used the Visual Studio Addin to create the VS projects and also to add Qt classes etc... so I don't have a .pro file.
[/quote]You can export the project to .pro file from vsaddin. This is part of the Qt menu in msvc. I have done my migration from msvc to Qt creator that way.
-
[quote author="JKSH" date="1369361247"]I found another previously-undocumented change:
- QPen now has a default width of 1 instead of 0, so it is no longer cosmetic by default.[/quote]
Ouch
-
[quote author="koahnig" date="1389278461"]
You can export the project to .pro file from vsaddin. This is part of the Qt menu in msvc. I have done my migration from msvc to Qt creator that way. [/quote]Thanks. But I continue to use Visual Studio with the addin.
I have seen that it is easier than I thought, it's almost "automatic", I have only to add the new modules using the addin and I have to change the names of the libraries in the project settings (eg QtCore4.lib -> Qt5Core.lib)
....
[quote author="JKSH" date="1369361247"]
- QPen now has a default width of 1 instead of 0, so it is no longer cosmetic by default.
[/quote]
mamma mia!!!!!! :(
- QPen now has a default width of 1 instead of 0, so it is no longer cosmetic by default.
-
ERROR: 'class QApplication' has no member named 'argc'
FIX for QApplication::argc():
@
s_argc = app->arguments().size();
@FIX for QApplication::argv():
@
s_argv = new char*[s_argc + 1];
//
for (int i = 0; i < s_argc; i++) {
// current arg
std::string arg =
app->arguments().at(i).toStdString();
// copy arg to char** structure
s_argv[i] = new char[strlen(arg.c_str()) + 1];
memcpy(s_argv[i], arg.c_str(),
strlen(arg.c_str()) + 1); // +1 for '\0'
}
s_argv[s_argc] = ((char)NULL);
@My two cents :-)
-
ERROR: 'class QApplication' has no member named 'argc'
FIX for QApplication::argc():
@
s_argc = app->arguments().size();
@FIX for QApplication::argv():
@
s_argv = new char*[s_argc + 1];
//
for (int i = 0; i < s_argc; i++) {
// current arg
std::string arg =
app->arguments().at(i).toStdString();
// copy arg to char** structure
s_argv[i] = new char[strlen(arg.c_str()) + 1];
memcpy(s_argv[i], arg.c_str(),
strlen(arg.c_str()) + 1); // +1 for '\0'
}
s_argv[s_argc] = ((char)NULL);
@My two cents :-)
-
ERROR: 'qWaitForWindowShown' is not a member of 'QTest'
FIX:
@
QWidget* panel;panel->hide();
panel->show();#if QT_VERSION >= 0x050000
QTest::qWaitForWindowActive(panel);
#else
QTest::qWaitForWindowShown(panel);
#endif
@ -
ERROR: 'qWaitForWindowShown' is not a member of 'QTest'
FIX:
@
QWidget* panel;panel->hide();
panel->show();#if QT_VERSION >= 0x050000
QTest::qWaitForWindowActive(panel);
#else
QTest::qWaitForWindowShown(panel);
#endif
@ -
ERROR: QSpinBox: No such file or directory
FIX: Add this in your .pro file:
@
equals(QT_MAJOR_VERSION, 5) {
QT += widgets
}
@ -
ERROR: QSpinBox: No such file or directory
FIX: Add this in your .pro file:
@
equals(QT_MAJOR_VERSION, 5) {
QT += widgets
}
@