I am happy to announce that Qt 5.7.0 Release Candidate is now available!
We are planning to release Qt 5.7.0 final release within coming weeks so please try RC now. All feedback is welcome! Please report new bugs to bugreports.qt.io. You can also send e-mail to Qt Project mailing lists or contact us via IRC.
More information about Qt 5.7.0 release can be found from Qt 5.7.0 new features page, Qt 5.7 Beta blog post or from the Qt Documentation snapshot.
If you have existing online installation, you can update Qt 5.7.0 RC by using maintenance tool. You can also download new installers (online or offline) from the Qt Account (for commercial users) or from download.qt.io.
Do you like this? Share it
Subscribe RSS
Why can’t I find the Wayland Compositor module in this RC ?? the wiki says that it’s in the tech preview modules but it’s not !
It is, in qtwayland submodule. See http://code.qt.io/cgit/qt/qtwayland.git/tree/src/compositor?h=5.7.0
i know it’s in the GIT source repo,
but it’s not available with the others modules in the Maintenance Tool !
Wayland and compositor API is part of src package only, no binaries. So if you install src package from online installer you got sources for compositor API as well
Good news!
Nice to see QWebEngine print support. Right now I see only support for pdf printing (QWebEnginePage::printToPdf())… Is there any plan to support printing directly to a printer also, that is the one feature that we need to move from WebKit to WebEngine.
Thanks,
Francois.
Hi, thanks for this RC.
Unfortunately, most of the Qt3D examples still don’t work as expected, at least under with msvc 2013 – 32bits (crashes on exit, missing resources, CPU overload). They probably aren’t up to date with the latest API of Qt3D.
I don’t think that a bugreport will change anything, examples are not used to have a high priority on JIRA while it’s the first gate to use the API…
@LaTer: There will be some fixes to Qt 3D examples and documentation still coming before Qt 5.7.0 final, but please do file the bugreport.
The new qtquick touch controls are just what I need. Awesome stuff! No I just need to convince my employer to get his head out of his butt and pay for a commercial licence.
Hello,
With this release Qt webengine is Chrome 50 based ?
Thank you for this work !
No, it is based on Chromium 49, with security fixes back-ported from Chromium 50 and 51.
how to fix this error Invalid property name “visible”. (M16). when creating Qt quick 2 controls application. also the qt quick controls not showing in the designer window.
This will be fixed for the final release.
You can apply this patch: https://codereview.qt-project.org/#/c/161045/
manually to the plugins.qmltypes for QtQuick Controls 2, since the fix is just editing a text file.
Is it necessary to rebuild Qt? I’ve replaced file “./5.7/gcc_64/qml/QtQuick/Controls.2/plugins.qmltypes” with one from branch 5.7.0, but it still complains `Invalid property name “visible”. (M16)`.
Is official Qt SSH support on your road map somewhere soon? I need to communicate with a server over SSH and the current work around I have found isn’t very nice so if you can support SSH natively that would be great. Thanks.
Something like android-clang-libc++ mkspecs is missing, any plans in Qt 5.7 or back porting in Qt 5.6?
Clang in the Android NDK suffers from a few issues that have to be worked around before we can support it in Qt. There is currently ongoing work for this in the 5.6 branch of Qt, so it should be supported in a future 5.6.x and 5.7.x release.