QML and Qt Quick

Or don't use states at all. import QtQuick 2.0 import QtQuickUltralite.Extras 2.0 Item { id: signal property bool show: false property bool showtwo: false Rectangle{ id: rect1; width: 50; height: 50; color: "green"; visible: !signal.show } Rectangle{ id: rect2; y:100; width: 50; height: 50; color: "red"; visible: signal.show } Rectangle{ id: rect3; x:100; width: 50; height: 50; color: "yellow"; visible: !signal.showtwo } Rectangle{ id: rect4; x:100; y:100; width: 50; height: 50; color: "black"; visible: signal.showtwo } Timer { running: true; repeat: true; interval: 1000 onTriggered: { console.log(signal.show); signal.show = !signal.show; signal.showtwo = !signal.showtwo; } } }

Thank you, good to know.

@fcarney We can write a core where you can espose all method to Qml. In this way UI can be adapted many screen without change the core.

@fcarney https://doc.qt.io/qt-6/qtqml-javascript-dynamicobjectcreation.html destroy() does exist. I would use loader to recreate treebuttonUnmappedIn when it is recalled.

@GrecKo said in QML_INTERFACE example: A QML_INTERFACE should not inherit from QObject Hi @GrecKo how did you determine this, can you point to some docs for further reading? I'm also confused by how these macros should be used correctly and in which circumstances. In my case I have a class A with some functions that are pure virtual. Subclasses of this are registered via qmlRegisterType(). I have another base class B with sub classes that are also registered. B has a property of type A.

Models in QML depend upon notification. This will update when changing things in the model because it has notification signals: ListModel { id: lmodel } Repeater { model:lmodel } This will not if you try and modify vmodel elements (unless the change causes the vmodel variable itself to change): property var vmodel: [1,2,3] Repeater { model: vmodel } So code like vmodel.push(4) won't provide signals to change for the repeater to see.

@jsulm said in best way to remember informations about opened files: calculate hashes from the content of both files using https://doc.qt.io/qt-5/qcryptographichash.html @tubbadu I don't believe you need any kind of cryptographic hash for your purpose of hash-content-for-compare. I believe Qt gives you an adequate implementation for your purpose in e.g. uint qHash(const QByteArray &key, uint seed = 0).

I know for a fact that it is possible to have QtQuick.Controls 2 if Qt is built from source I was looking for a simpler way to install Qt (apt-get) and run a project of my own but if quickcontrols2 doesn't allow it, I'll just have to continue with the online installer option Thank you both, I'll close the topic if there isn't anything to add

I'll try, thanks!

@J-Hilk By groping I found that the QtQuick I need to use with my setup was 2.3, but thanks for explain me the difference between versions

@aim0d On what OS? You can download installer from here: https://download.qt.io/archive/qt/5.14/

For the purpouse of people who might search for an find this forum post, I put in a request with QT support and received the following. Hi Joe, Thank you for contacting Qt Support and for providing your sample project. There are 2 broad ways to specify the fragmentShader property, depending on which version of Qt you want to target: The Qt 5 way is to specify the shader's source code as a string. The Qt 6 way is to pre-compile your shader source code into a .qsb file, and specify a URL to that .qsb file See: https://doc.qt.io/qt-5/qml-qtquick-shadereffect.html#fragmentShader-prop https://doc.qt.io/qt-6/qml-qtquick-shadereffect.html#fragmentShader-prop To do it the Qt 5 way, the easiest approach is to copy the contents of your .frag file and paste it as a string literal (surrounded by quotation marks) to the RHS of the "fragmentShader" property. To do it the Qt 6 way, run the QSB tool to compile your shader source code. Unfortunately, the code of colour_wheel.frag is too old to be supported by QSB (for example, the "varying" keyword was deprecated long ago, and even removed for ES profiles) See: https://doc.qt.io/qt-6/qtshadertools-overview.html https://doc.qt.io/qt-6/qtshadertools-qsb.html I hope this helps.