-
Bug
-
Resolution: Moved
-
P3: Somewhat important
-
None
-
QDS 4.4
-
None
-
Windows
-
99fcb5c14b6cb29e3d6ac64eec9b5239951795ec
-
QDS Berlin - 2024 Week 19/20, QDS Berlin - 2024 Week 21/22
The project is attached to this report.
Executing qml2puppet-4.4.0.exe with --config option shows an error like this:
C:\Users\81808>C:\Qt\Tools\QtDesignStudio\qt6_design_studio_reduced_version\bin\qml2puppet-4.4.0.exe --qml-runtime -I C:/Users/81808/Documents/Simulink_Qt/SimulinkQtUI/imports -I C:/Users/81808/Documents/Simulink_Qt/SimulinkQtUI/asset_imports --apptype widget --config C:/Users/81808/Documents/Simulink_Qt/SimulinkQtUI/qtquickcontrols2.conf C:/Users/81808/Documents/Simulink_Qt/SimulinkQtUI/content/App.qml QML debugging is enabled. Only use this in a safe environment. Info: Starting QML Runtime ((null):0, (null)) Warning: QQmlComponent: Component is not ready ((null):0, (null)) Critical: qml: Error loading configuration file: %s ((null):0, (null))
The qtquickcontrols2.conf exists in the path.
The reason why I thought this is an error is because of the error message: usually there is a path instead of "%s." I'm suspecting the path is not currectly handled inside the code.
By the way, the reason why I tried to specify --config for qmlpuppet in the first place was because the Qt Quick Controls' styles were different when the app was launched from QDS and from qmlpuppet in cmd.
<QDS>
<qmlpuppet in cmd>
- resulted from
-
-
- Closed
-
- mentioned in
-
Page Loading...