Thank you very much @oliver_mpt I get the same problem trying to compile CopyQ 14.0 against Qt 6.11.0 on Windows 11. Thank you very much @JonB I was using version 11 and tried using a newer MinGW-w64, and I managed to compile using version 14. But it fails to link. I'm too ignorant about Qt, C++ and C toolchains to judge, but there is a good chance that going from version 11 to 14 suffices to fix that specific issue. I did not need to define NTDDI_VERSION. Unfortunately I do not know for sure because I got version 14 from MSYS2 instead of Qt, so they're very different beasts, which is very likely to explain the linking failure. How were you able to get MinGW-w64 13 from Qt? One thing I noticed is it's complicated to see which version of MinGW-w64 a directory contains. License

Ha, good one! Of course QString needs to go :D I propose to replace it with AiString which just automatically knows what data it should hold based on the context. The only downside is when servers are down or the model starts hallucinating, but it is only a minor annoyance.

In QDS, SVGs usually look blurry when the path is being scaled instead of rendered at its native size. Make sure the SvgPathItem matches the original SVG viewBox and avoid scaling it down inside the component. If possible, import the SVG as a file and use an SVG Image element rather than pasted path data, and keep width/height proportional to the source. This prevents QDS from rasterizing it at a low resolution.

Found it. I overlooked the following traceback in the logs. Traceback (most recent call last): File "/mnt/ssd2/develop/experiments/python-squish/mysquishtest.py", line 16, in <module> squishtest.waitForApplicationLaunch() RuntimeError: Waiting for application timed out When I remove the call squishtest.waitForApplicationLaunch() it works and I can use squishtest.test.compare() to test conditions.

I am thrilled to share that we have published new tests in the Qt certification platform. Currently, the following tests are available: Qt Foundation (6.8 LTS): This exam validates your understanding of key Qt programming concepts. The exam is aimed at fluent Qt developers who are confident in their working knowledge and want to get a proof of their skills. Qt Quick Developer (6.8 LTS): Focuses on essential QML language concepts, and is well suited for fluent developers who want to demonstrate their practical skills in crafting user interfaces with Qt Quick. Qt Quick Specialist (6.8 LTS): This advanced certification covers mastery of advanced Qt Quick and QML development techniques, and is ideal for experienced Qt developers who want to demonstrate deep technical knowledge of Qt Quick and QML. Qt Application Developer (6.8 LTS): Designed for developers focusing on Qt application logic and backend functionality. This exam validates your proficiency in core C++ development with Qt. A Qt Student Developer test is currently under development. This test is specifically designed for students and those new to professional Qt development, who want to get a tangible proof of their Qt skills for employers and peers. Register and find full test details at qt.io/qt-certifications.

@jkobus Hi, wow, thanks for coming back to my topic and your effort you put into the example :) Yeah was definitely missing something like Task Trees in Qt back then. Maybe I will visit my project again and see what I can do using the new Qt Task Tree features :) Thanks again :)

环境： RK3588J + ubuntu20.04 + QT6.8.3 在测试中： 1、使用eglfs可以正常显示qtbase的测试用例； 2、但是在使用xcb时，只有边框，但是边框里面是黑屏。 3、如果改成QT_QUICK_BACKEND=software后，xcb时可以正常显示。 4、使用QT5.15的qbase示例时，XCB可以正常显示，且GPU加速渲染 我想请问一下，在使用QT6.8.3时，使用XCB，GPU无法正常加速渲染是因为我编译源码时有问题，还是RK3588J的mali和QT6.8.3的XCB时GPU渲染有兼容性问题？

Hello just wanted to let you know that on https://qt-mirror.dannhauer.de, the SSL certificate is expired.