QML and Qt Quick

Test this out with a QML ListModel with the same QML. I don't think all properties on a QObject are automatically turned into properties the ListView delegate can see. Otherwise it would pollute the delegate namespace. To get the values out of the QObject you will have to use modelData.<property>. You could try that in section.property to see if that will work. "modelData" for a "list" used as a model is the property it injects. For a "proper" model you would need to base off of QAbstractListModel or similar. Then the properties you see are defined in roleNames function. Try this to see if this is what is happening (not sure if this would work though): section.property: "modelData.label" Edit: I think I said something badly: When using a list of some sort (QList, [], etc) that is not based upon one of the abstract models. The injected delegate property is called "modelData". This would be each item from the list in that property. So in your case it would be the LandmarkViewModel object.

Finally, I have implemented this using QXlsx https://github.com/QtExcel/QXlsx library for reading MS Xlsx file and store it in the below DS to load data mentioned in post image above: QMap<QString, QMap<QString, QString>> m_langTransMap; QMap<Input String,QMap<LangName,TranslatedText>> Use of Own Translator: QML: Text{ text: myTranslator.getTranslatedText( "Main Controller") + myTranslator.emptyString] } class TranslationHandler : public QObject { Q_OBJECT Q_PROPERTY(QString emptyString READ getEmptyString NOTIFY languageChanged) public: void TranslationHandler::loadTranslationData() { /// Read Excel Data /// load it into QMap emit languageChanged(); } Reference Link: https://wiki.qt.io/How_to_do_dynamic_translation_in_QML https://www.kdab.com/wp-content/uploads/stories/QmlComponentDesign-TwoWayBindingProblem-AndreSomers.pdf Read Cell Data: https://github.com/QtExcel/QXlsx/blob/master/TestExcel/extractdata.cpp https://github.com/QtExcel/QXlsx/blob/master/TestExcel/hello.cpp

It looks like there is a precedence: import QtQuick 2.15 import QtQuick.Window 2.15 import QtQuick.Layouts 1.15 import QtQuick.Controls 2.15 Window { width: 640 height: 480 visible: true title: qsTr("State Precedence") Text { text: rect.state } RowLayout { anchors.fill: parent ColumnLayout { Layout.preferredWidth: 150 Layout.fillHeight: true Repeater { id: staterepeat model: 5 delegate: CheckBox { text: "state %1".arg(modelData) } Component.onCompleted: { for(let ind=0; ind<model; ++ind){ let nstate = rect.states[ind] nstate.when = Qt.binding(()=>itemAt(ind).checked) } } } } Rectangle { id: rect width: 200 height: 200 border.width: 1 states: [ State { name: "state 0" PropertyChanges { target: rect color: "red" } }, State { name: "state 1" PropertyChanges { target: rect color: "blue" } }, State { name: "state 2" PropertyChanges { target: rect color: "green" } }, State { name: "state 3" PropertyChanges { target: rect color: "yellow" } }, State { name: "state 4" PropertyChanges { target: rect color: "orange" } } ] color: "black" } } } Items that appear first in the list have precedence vs things that appear later.

Hi and welcome to devnet, From a quick search, QtQuick WebGL is not available at all in Qt 6 currently. See here for the comparison and explanation. Depending on what you are developing, Qt for WebAssembly might be a possibility.

I should point out, that you could use a push instead of a replace. Then have a back button that pops the last one off to go back. So you could use it the same way except with depth instead of how I did it.

This doesn't seem to be implemented. Setting Qt::Popup doesn't work for QQuickView, and doesn't work for QQuickWidget, either. A workaround is to use a plain QWidget as popup, and add a QQuickWidget as child.

@jsulm Ok I didn't understand what this sentence actually says. Thanks for pointing out!

@GrecKo I was trying to find a way to execute an animation without declaring it separately. In "meta-code": onSignalTrigger: { timer.stop() doSomething() doSomethingElse() // animate property PropertyAnimation { target: theObject; property: "opacity"; to: 0 } } The long way is: PropertyAnimation { id: myAnim; target: theObject; property: "opacity"; to: 0 } onSignalTrigger: { timer.stop() doSomething() doSomethingElse() // animate property myAnim.start() } I find the first syntax is more readable

@J-Hilk - sorry, scrap that last comment, I changed it to value and now it works!, yay!!, thank you @J-Hilk, you sir are a genius!! :)