Hi all! Currently, Qt creator only updates on project changes (re-parsing CMakeLists.txt, configuring, generating etc.) when the IDE is in the foreground. Is there a way to configure that? I often work on multiple branches in multiple windows (and IDEs), letting AI add new files in one branch while I work on another. When I switch to the instance of Qt Creator with those new files, it starts to parse, which means waiting for 1-2 minutes instead of me hitting the ground running, and immediately starting to implement.

@Kaj-Gronholm Thank you for clarifying. It seems to me that the rest of the QCanvasPainter does take devicePixelRatio into account. If you call the QCanvasRhiPaintDriver::beginPaint method that takes logicalSize and dpr parameters, the painter will automatically scale points and line widths, so that the drawing looks the same across different dpr screens. I have confirmed this with testing. The main difference in behavior I would expect is for QCanvasPainter::drawImage(const QCanvasImage &image, float x, float y) to draw the image based on the logical dimensions (dimensions / image_dpr). So, if I've created a QCanvasImage from a QImage with dpr=2, these should be equivalent: painter->drawImage(retinaImg, x, y); painter->drawImage(retinaImg, x, y, retinaImg.width() / 2, retinaImg.height() / 2); Or, put another way, if I had a @1px image and painted it with painter->drawImage(img, x, y), and then replaced it with a @2px or @3px image, I would expect it to take the same amount of logical space on the screen.

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.

Hi everyone, We work on developing enterprise learning and training platforms, and recently we’ve been exploring Qt for building desktop or device-based applications that support safety training use cases. In industries like oil & gas—especially in regions such as the UAE—safety training systems often need to support offline access, structured learning modules, controlled user roles, and reliable performance across different environments. We’re interested in understanding from the community: Has anyone used Qt for building training, compliance, or safety-related applications? How well does Qt scale for enterprise-focused learning or content-driven platforms? Any best practices or architectural considerations when using Qt for regulated industry use cases? This is mainly an experience-sharing and learning discussion. Looking forward to hearing your insights. Thanks!

@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.