Details
-
Bug
-
Resolution: Fixed
-
P1: Critical
-
Qt for MCUs 2.5
-
None
Description
I'm using Windows 11 with the QDS installed with qt-designstudio-windows-x64-4.1.0_723.exe .
<Background>
In QDS4.1 for Qt for MCUs project, when the playbutton is clicked, compilation checks should be activated and the user should be able to find the issues at earlier stage before compiling the project in Qt Cretor(QC).
blog link to this feature(Qt for MCUs support section) : https://www.qt.io/blog/qt-design-studio-4.1-released?hs_preview=zdlNWDFn-115137686790
So I created a MCU project and pasted this code to Screen01.ui.qml. (In "Code" of this editor, somehow change line doesn't work, so I just paste the code as is here)
/* This is a UI file (.ui.qml) that is intended to be edited in Qt Design Studio only. It is supposed to be strictly declarative and only uses a subset of QML. If you edit this file manually, you might introduce QML code that is not supported by Qt Design Studio. Check out https://doc.qt.io/qtcreator/creator-quick-ui-forms.html for details on .ui.qml files. {}/{*} import QtQuick 2.15 import Constants 1.0 Rectangle { width: Constants.width height: Constants.height color: Constants.backgroundColor Text { id: text1 text: qsTr("Hello DifferenceQDS_QC") anchors.centerIn: parent // Note: This property is only generated when it has a binding. // rotation: 0 } NumberAnimation { target: text1 property: "rotation" loops: -1 duration: 10000 running: true to: 360 from: 1 } }
Now, according to the limitation of Qt for MCUs that rotation property should have a biding to it for the animation to get triggered against it, this code should not compile. (To make it compile, one should un-comment out the "rotation: 0" in text1.
ref : https://doc.qt.io/QtForMCUs-2.4/qtul-qtquick-api-differences.html#known-issue-scale-rotation
But when I clicked on the play button next to the Live Preview button, the application ran without any compilation errors.
The console output is here.
20:54:45: Running steps for project UntitledProject6... 20:54:45: Starting: "C:\Qt\QtMCUs\2.4.0\bin\qmlprojectexporter.exe" C:/Users/81808/work/Study/QDS/UntitledProject6/UntitledProject6.qmlproject --platform qt --toolchain mingw --include-dirs "C:/Qt/QtMCUs/2.4.0/include/qul,C:/Qt/QtMCUs/2.4.0/include/qul/Timeline" --outdir C:/Users/81808/AppData/Local/Temp/QtDesignStudio-TtlRgJ [qmlprojectexporter] warning: Problem during load of qmlproject file [qmlprojectexporter] C:/Users/81808/work/Study/QDS/UntitledProject6/UntitledProject6.qmlproject:9:5: warning: It is not recommended to use the 'directory' property. The build system might not be able to correctly track the contents of the directory, so always clean and rebuild whenever adding or removing files. Additionally, every file present in the directory at configure time will be added to the application binary, which might increase the memory footprint. Prefer explicit inclusion of the needed files using the 'files' property to avoid these issues. QmlFiles { ^~~~~~~~ [qmlprojectexporter] C:/Users/81808/work/Study/QDS/UntitledProject6/UntitledProject6.qmlproject:17:5: warning: It is not recommended to use the 'directory' property. The build system might not be able to correctly track the contents of the directory, so always clean and rebuild whenever adding or removing files. Additionally, every file present in the directory at configure time will be added to the application binary, which might increase the memory footprint. Prefer explicit inclusion of the needed files using the 'files' property to avoid these issues. ImageFiles { ^~~~~~~~~~ 20:54:48: The process "C:\Qt\QtMCUs\2.4.0\bin\qmlprojectexporter.exe" exited normally. 20:54:48: Elapsed time: 00:03.
By the way, I commented out quickVersion, qt6Project and qdsVersion from qmlproject file in order to workaround this issue : https://bugreports.qt.io/browse/QDS-9876
My Qt for MCUs SDK is registered as follows.
And here is the Kit I'm using.
Now, there's a customer requesting this "checking the Qt for MCUs' compilation errors on QDS" feature and they expect this to be availabe in June.
Could this be resolved by then? or is there any quick workaround?