We have released Qt 6.7.2. As a patch release, Qt 6.7.2 does not introduce new features but contains more than 200 bug fixes, security updates, and other improvements to the top of the Qt 6.7.1 release. See more information about the most important changes and bug fixes from Qt 6.7.2 release note.
Get Qt 6.7.2
As earlier, you can add Qt 6.7.2 to the existing online installation by using the maintenance tool or do a clean installation by using the Qt Online Installer, which can be downloaded from the Qt Account Portal (for commercial users) and from the opensource download area (for opensource users).
In addition, Qt 6.7.2 source packages are available in the opensource download area for opensource users. For commercial users, the Qt 6.7.2 offline installers and source packages are available in the Qt Account Portal.
Provide feedback
For any issues you may find, please submit a detailed bug report to bugreports.qt.io or contact our technical support team in case you have a support plan with your commercial license. You are also welcome to join the discussions in the Qt Project mailing lists and developer forums.
Qt 6.7 release plan
We will continue releasing new patch releases to the Qt 6.7 series. The target is to release Qt 6.7.3 by the end of August 2024, see more information from the Qt 6.7 releasing pages.
Commenting for this post has ended.
I have been waiting for this one. Very nice
Please fix the broken scroll speed in qml that was introduced in this release https://bugreports.qt.io/browse/QTBUG-116388
[What's New in Qt 6.6 | Qt 6.7|https://doc-snapshots.qt.io/qt6-dev/whatsnew66.html#qt-quick-module] In this section look at QTQUICKFLICKABLEWHEELDECELERATION . You can go back to the previous implementation. I think for the current implementation there are other improvements to be made. I'm going to look into it the coming week. From what I can see they tried to make scrolling directly proportional to the scrollwheel angle instead of using innertia with flickvelocity. I like that change but they made a mistake in that fix where if you scroll fast right now the displacement is less than when you scroll slow.
But the new version should not ignore the flickDeceleration entirely, right? Doesn't matter what values you put in, it always stays the same. I tested this on Linux and Windows. If not, then the documentation is outdated because it does still state example values https://doc-snapshots.qt.io/qt6-dev/qml-qtquick-flickable.html#flickDeceleration-prop
As far as I understand it, it does ignore flickDeceleration for Mouse Movements specifically as they only position the view and do not rely on innertia anymore. My guess is the flick innertia only makes sense on a touch screen and those magic mouse touch inputs, but when you use a scrollWheel on a normal mouse that idea of flinging the paper just shouldn't apply. It's called a 'Scroll' wheel for a reason, the UX thought behind it was scrolling those old paper scrolls. With a touch screen when you flick you actually release your finger and the whole flickdeceleration is based on the UX idea of you pushing and releasing a surface with innertia.
Yes, this was the intention behind it! Prior to 6.6, wheel events would call flick() internally, which essentially means that mouse wheel events would be treated the same as flicking with a finger. We didn't like it, which is why we changed it. I'm still not entirely happy with the new behavior, and plan on improving it further in a later release. I want it to feel similar to browsers and other common applications that have a scrollable area. Finger/Stylus based flicking will be left unchanged.
So the Qt 6.6 version that was released on 04.10.23 is the final version? According to MaintenanceTool it is.
Yes, final version is build 4.10.23
What's the licence for Qt Graphs?
GPL3 / Commercial
"except Wayland-based systems" Why? I will waiting Wayland...
Hi Andrei. Due to technical difficulties, screen capture on Wayland is not yet implemented, but this is something we will be looking into for future releases.
In Qt we trust!
What is the latest usable version for open source users ? I see that I can only download 6.2.4 for now.
6.3, 6.4, 6.5 and 6.6 are all downloadable for open source users. Try reinstalling Qt maintenance tool
I think that there is a problem with my account. Even when I try to install Qt to a new computer, the latest version available is 6.2.4.
Hi! There are no visibility restrictions for open-source users, so you should also be able to see the Qt 6.6.0 and earlier releases. Please create a bug report with an installation log ( start the online installer from the command line with --verbose) so we can study your problem more.
I am also unable to see 6.6 listed in the maintenance tool. I can only see up-to 6.5.3. I currently have installed 6.5.0. I am using Linux x64.
Try re-installing the SDK.
Maybe you should also keep care of such serious bugs:
https://bugreports.qt.io/browse/QTBUG-87334
If you want to support responsive ui for mobile devices you should keep the basic stuff working.
You are right. I tried to reproduce it on Qt 6.6.0, but maybe I did something differently or interpreted the result wrong, because with the example that was there I was not able to reproduce it. If you have tips and tricks to reproduce it please drop in the ticket! Thanks.
So, Qt for Python still doesn't work on Android and ARM64?
Hey Ruslan, it will work on aarch64 (linux) once the wheels are out. It's taking a bit of extra time due to some last minute CI and dependencies issues. If you meant Apple Silicon ARM then it has been working since 6.2.2 Qt for Python works to deploy apps to Android since 6.5 https://www.qt.io/blog/taking-qt-for-python-to-android but 6.6 brings simpler steps to deploy your apps. Stay tuned :)
Thanks a lot! Sound very interesting because on https://wiki.qt.io/Qt_for_Python still present > Please notice that Android, iOS, and WebAssembly are not supported yet.
When I install Qt 6.6 on MacOS Catalina, I get an error during the installation process: (qt.qt6.660.clang64): Could not find the required QmakeOutputInstallerKey(qt.qt6.660.clang64_qmakeoutput) value on the installer object. The ConsumeOutput operation on the valid qmake needs to be called first.
Hi! macOS Catalina isn't supported in Qt 6.6.0, see https://doc.qt.io/qt-6/supported-platforms.html
The speed with which Qt development is moving lately is exciting, it's hard to keep up with all the new stuff.
Any chances that Qt for Python will support WASM via Pyodide sometime in their near future?
Hi! I tried version 6.6 of Qt. Now when I want to capture an image or save a video to a file on Android 10 (Infinix), the application crashes, but on Windows 10 PC it works correctly. Why doesn't it work on mobile?
Ouch.. hard to speculate the reason very accurately without further information. Do you mind to drop a bug into https://bugreports.qt.io ?
If you don't mind, please add the steps to reproduce (perhaps a screen record), an example app (or at least code snippet) and background information (adb shell getprop - at minimum the system.build and ro.product.model and ro.product.manufacturer) from you emulator or target device.
Most of the Windows retrieved by QWindowCapture::capturableWindows() display an abnormal black background, This api is still unavailable, at least on Windows 11.
Thank you for letting us know about this problem Junchong Tang. I created a bug report for this at https://bugreports.qt.io/browse/QTBUG-118536, but we need some more information from you. Could you please have a look and update it with all the details you may have?