QML and Qt Quick

Thanks to Mitch Curtis. He answered me: However, it's working as expected: the size of the Button is as you requested. However, because the Material style Button uses positive insets for the elevation drop shadow effect, the background is pushed inwards: https://doc.qt.io/qt-6/qml-qtquick-controls2-control.html#control-layout Oh, right, I forgot to mention the solution: set topInset and bottomInset to 0.

Maybe you should use DelegateModel. eg: TableView { model: DelegateModel { model: xxx delegate: xxx } }

@sierdzio I found it...because I used Component "SerialPort" for each Item. So that created new Object . I try change qmlRegisterType -> QQmlComtext and it worked ...Thank you for your supporting. Have good day!!

Most probably, yes.

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).