QML and Qt Quick

@dheerendra Thank you for your reply. I do not use TableView from Controls 1. Instead, TableView: QtQuick is applied. Flickable is not the issue. Touch event handling in Qml is the problem. Mouse works just fine.

The consensus seems to not have to rely on Array.isArray : https://bugreports.qt.io/browse/QTBUG-125289

@feli223 This post doesn't say anything about how the resources have actually been populated. That's where it went wrong. The fact that it works without the colon means, that an in-source build finds the file somewhere in the source tree. If the application is deployed without its sources, it won't work any more. I don't know where, how, and why it went wrong, because this part of the code is missing. That means I can't help you, probably nobody can. But I do know that the resource system works seamlessly. So I pointed you to the documentation, because my feeling is that you haven't read it fully and made a small mistake..

Better you provide one sample. Difficult to imagine what you would like to achieve. It is possible to do. One simple example is here. main.qml Window { width: 640 height: 480 visible: true title: qsTr("Hello World") MyQmlPropertyMap{ id : owner} Text { text : owner.name } MyButton{ b1 : y1 } YourButton{ id : y1 visible: false } } MyButton.qml Rectangle { width: 200;height: 200 color: "blue" property var b1 MouseArea{ anchors.fill: parent onClicked: { b1.visible = true } } } YourButton.qml Rectangle { width: 100;height: 100 color: "red" }

It turns out that I was using the wrong call on my proxy model. This works: void SanitizerModel::setSpaceIndex(int index) { if (m_spaceIndex == index) { qDebug() << "SanitizerModel::setSpaceIndex: skipped"; return; } m_spaceIndex = index; invalidateFilter(); // *** NOT invalidateModel() *** } Thanks to all who looked at this.

@CKurdu said in What is the problem in this qml file?: The problem is that my coworker insists that the lines below are correct. Connections { target: videoRecords visible: false pageManager.show("videoRecordsPage") } What is this even supposed to do? Connections is meant to connect to signals declared in its target. Note that there is little reason to use a Connection inside the declaration on its target. There's no visible property in Connections, it's not a visible item. Writing pageManager.show("videoRecordsPage") here is syntactically incorrect in QML. You also have a duplicate object id. The correct syntax for Connections is : Connections { target: object function onSignalName() { // do stuff } } Here you don't need Connections to handle a signal of videoRecords, you could do: VideoRecords { id: videoRecords visible: false modal: true on<YourSignalName>: pageManager.show("videoRecordsPage") } This is assuming that you want to handle a signal in VideoRecords and show the videoRecordsPage after. You are the one knowing if it does make sense in your code. As for the visible: false in Connections, maybe it was meant to be the enabled property? Your tell us (or your colleague tells you).

It's in Qt Positioning.

Thank you for your reply. Yes, I'm currently running the example(simplerhiwidget) for testing purposes and I am sure that my app started and running normally. Is there any parameter I need to modify to enable RenderDoc to inject its DLL into the executable? Also, in the remote host manager, there's nothing I can select; is this normal behavior? [image: 61a883da-e55c-43c9-9ad1-93009acca5d3.PNG]

If you are trying to create a cube then it looks like your cube data is wrong as you can see from this picture: [image: 2567a1f1-8200-4647-8e5d-026f709ee0a4.png]

After removing anchors.centerIn: parent from the Label and changed it to anchors.fill: parent the problem was fixed.

I solved this after a few attempts using ChatGPT, not what I wanted ultimately, but manually I really struggled with this.

You could add this margin in the header component itself. ListView leftMargin can't be used here since it puts the margin on the left of header. If using a Control as the header you could use rightPadding or rightInset to easily add a inside margin.

@J-Hilk Thank you for your reply, Indeed, after I discovered that the "nativeEvent" inherits from the "QWidget", I tried something else, as you said, using the "NativeEventFilter" that inherits from the "QCoreApplication ", but the problem remained. How can I modify and adjust it