Hi, You should check the bug report system as well as take a look at the history of the Qt Creator sources to see if something has changed in that regard.

Hello, QxOrm library 1.5.1 and QxEntityEditor application 1.2.9 just released. QxOrm library 1.5.1 changes log : Support latest versions of Qt and boost (Qt 6.10 and boost 1.90) : fix compilation issues and remove several warnings Provide several development-ready Docker images and containers : SQLite, MySQL, MariaDB, PostgreSQL, MongoDB More details about QxOrm and Docker containers : https://hub.docker.com/u/qxorm Improve QxOrm JSON API : possibility to provide a query in JSON format (useful for MongoDB database) Fix error converting registered object from JSON with column filter Improve QxService and QxHttpServer modules : new class qx::service::QxConnectOther to define several connection parameters (for example to create several servers, GitHub #34) New method in qx::QxSqlQuery class named setFctOnAfterSqlExec() to define a custom callback function called after SQL query execution (can be used to get deleted items for example) QxEntityEditor application 1.2.9 changes log : Update QxEntityEditor application dependencies : Qt 6.10, boost 1.90, QxOrm 1.5.1 on all environments (Windows, Linux and macOS) QxEntityEditor macOS version is now a *.dmg file Remove QxEntityEditor Windows 32 bits and Linux 32 bits versions Remove QxEntityEditor javascript debugger (due to Qt6 dependency) : print logs inside custom scripts to debug [image: qxee_sample_small.png] You can download latest version of QxOrm library and QxEntityEditor application on QxOrm website. QxOrm source code is also available on GitHub.

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渲染有兼容性问题？

Yup, they're good for me, now, as well. I'm in the US on Verizon home internet service, so I wouldn't expect any... well, anything regarding network restrictions to be in play.