QML and Qt Quick

@AnttiK Thank you for your reply! :) Yes, i do something like that in my real program. First i show a dummy version of my gui (very fast and satisfying), then i create and register a bunch of stuff (about 1s), then i load the qml stuff (about 1s) and finally hide the dummy version. It appears like the app is instantly open and ready. The progress is more for eventually long running operations. I don't want to optimize. My problem is, that the forceUpdateSimple() method fails. The dummy version and the progress text are not displayed. And my "solutions" are more the result of trial-and-error than the result of knowledge...

Almost forgot to paste the qtbug: https://qt-project.atlassian.net/browse/QTBUG-143886 Seems they put it to Critical P1.

@AnttiK said in With Qt 6.10.1 and CMake, configuring a simple QML application fails when source code is in a folder with whitespaces: I'm afraid I'm not too familiar with the Qt sources and how they're organized so I'm far from certain whether my pull request or suggestion would even be considered. Don't be, every contributor had to start somewhere. It does not require a big complicated patch to get on the train :-)

If you know how to calculate the total of your delegates' height, you might want to handle the ScrollBar yourself and set its size and position manually. The position might be trickier to compute.

I don't know why I though update() was a method of the FBO::Renderer. I changed it now, and I'm having the same issue. Image gets temporarily rendered when resizing the widget, and then goes back to blank. EDIT: Oh, actually, it was my own fault. Was calling canvas->flush() which deletes the canvas after drawing. :facepalm:

@JKSH Oh that definitely sounds good

@FishBoneEK said in Need guide on modifying Qt modules: @SGaist I'm considering adding gaps in LineSeries of QtGraphs (with qQNaN() perhaps), instead of using multiple LineSeries. OK, so this is a continuation of https://forum.qt.io/post/836004 As mentioned there, this feature is coming to Qt 6.11 (currently downloadable as a beta) -- please give that a try before editing Qt.

Slightly off-topic: Maybe it's a typo, but Earth's gravity is 9.81 and not 9.18.

https://doc.qt.io/qt-6/qtqml-javascript-hostenvironment.html#type-annotations-and-assertions It says: Note: In QML, enumerations are not types and can therefore not be used as type annotations. Their underlying numeric type, int or double, should be used instead.

Have you tried a HoverHandler?

This behaviour is still not documented (Qt Bug Tracker). The special modifier handling is implemented in QWindowsPointerHandler::translateMouseWheelEvent. A WM_MOUSEWHEEL event is treated like a WM_MOUSEHWHEEL event: const QPoint angleDelta = (msg.message == WM_MOUSEHWHEEL || (keyModifiers & Qt::AltModifier)) ? QPoint(delta, 0) : QPoint(0, delta);

@ECEC said in Bind to another model's data in a delegate: @jeremy_k , A proxy model can only have one source though, so surely this would still require connecting to model B's dataChanged to be aware of relevant changes (i.e units changed)? QAbstractProxyModel::setSourceModel() only accepts one model. That doesn't mean that a proxy must use or limit itself to this interface.

@petero3 Thanks for the update. Because we have to stick to older Qt version I found workaround to use QQuickPaintedItem. Visually it gives me the same effect and CPU impact (if any) is bearable. ... only hands were dirty :-)

@huy2910 Any reason not to use more recent Qt version? Especially when using most recent Android version.