Details
-
Bug
-
Resolution: Unresolved
-
P3: Somewhat important
-
5.15.6, 6.2.0 RC
-
None
Description
It's always been that way: if you try to use a relative path there, it will try to load the container QML from the current working directory rather than from the directory containing the config file.
~/expt/qtquick Qt 6.3.0 in /home/rutledge/dev/qt6-dbg/qtbase [zen][21:10:28] qml -c simplest text.qml [ 0.000 W] default QQmlComponentPrivate::beginCreate - QQmlComponent: Component is not ready: QUrl("file:///home/rutledge/online/expt/qtquick/ItemWrapper.qml") qml: Did not load any objects, exiting. ~/expt/qtquick Qt 6.3.0 in /home/rutledge/dev/qt6-dbg/qtbase [zen][21:14:21] cat ~/.config/QtProject/Qml\ Runtime/simplest/configuration.qml import QmlRuntime.Config 1.0 Configuration { PartialScene { itemType: "QQuickItem" container: "ItemWrapper.qml" } }
(to be able to see even this much information requires fixing QTBUG-96801 first)
ItemWrapper.qml is in ~/.config/QtProject/Qml Runtime/simplest/ , alongside the configuration.qml file. That's the most intuitive place to put it.
Attachments
Issue Links
- relates to
-
QTBUG-96801 creating qml custom configurations is difficult because of poor error messages
-
- Reported
-
-
QTBUG-110112 Runtime qml won't load certain root elements
-
- Closed
-