QML and Qt Quick

@fcarney - thanks again, this is taking shape now. There are a few odd behaviours which I will try to nail down, but largely, I am now able to edit price, name and type, close and open again with all my changes being present! yay! Regards,

@Crisian-Adam-0 I have verified that the file does exist at that location. I receive the same errors when attempting to run in Release mode.

@raven-worx So what you are saying is what I said in the first few lines of my post, that I have to write what has already been written, is already documented by Qt as existing, is a direct reflection of what already exists in C++ because Qt decided to wrap it up in a "special" Neptune UI package. Not that it does ANYTHING relative to 3D or provides ANY additional information beyond that in the C++ class, so it in no way justifies a "special" package. But sure, why not use C++ to do what QML fails to do. Or why not just use a Qt Python package if you want your UI development to be separate from your core. Sort of removes having to dance around the not complete javascript to add a bit of functionality.

@MaruthiMarsh create a singleton componen: https://wiki.qt.io/Qml_Styling#Approach_2:_Style_Singleton

well I suppose it is not possible... I'm redrawing all the items (delegates). As an update() is not doing the job, I'm using a "fake" binding like suggested here.

@Praveen-Illa EGLFS can only display a single window. thus your splash screen cannot be also a window. you must make it an Item and place it above the content of the mainwindow. E.g. as a child of the windows's overlay for example

After some hour's a found a way todo this. Worklfow: DoubleClick on cameraPane (Expand) cameraPane.Layout.preferredWidth and cameraPane.Layout.preferredHeight is set to parent w, h other cameraPane opacity is set to 0 DoubleClick on cameraPane (Shrink) cameraPane.Layout.preferredWidth and cameraPane.Layout.preferredHeight is set to 0 other cameraPane opacity is set to 1

@r3d9u11 so, finally I've replaced ScrollView with Flickable and made function, that is refreshing content size. children elements call it manually: Flickable { id: fieldMap anchors.fill: parent ScrollBar.horizontal: ScrollBar { active: true; onActiveChanged: { if (!active) active = true; } } ScrollBar.vertical: ScrollBar { active: true; onActiveChanged: { if (!active) active = true; } } function refreshContentSize() { fieldMap.contentWidth = fieldMap.width; fieldMap.contentHeight = fieldMap.height; for (var i = 0; i < fieldMap.contentItem.children.length; ++i) { var item = fieldMap.contentItem.children[i]; var itemX = item.x+item.width; if ( itemX > fieldMap.contentWidth ) fieldMap.contentWidth = itemX; var itemY = item.y+item.height; if ( itemY > fieldMap.contentHeight ) fieldMap.contentHeight = itemY; } } } Maybe there is better solution

Hi, That's because widgets are not meant to be embedded like that. You can check KDAB's Declarative Widget project to mix widgets and QtQuick.

@EmadDeve20 said in Why I cant Play Audio Files? My Code is on armbian os in orangepipluse2 device: armbian I know, but Armbian is based on Debian und Ubuntu too, so usually package names are same. Good that it works now!

@jsulm thanks for your answer actually my android's developer option was enable but not now i enable this and this worked

@Pieter-Cardoen the qml engine only support this types: https://doc.qt.io/qt-5/qtqml-cppintegration-data.html if you want to support a custom type you will have to convert it to one of those. before you can process them in QML. For example a struct can be converted to a QVariantMap, or a custom class must interhit QObject and use the meta object system (properties, invokabkle methods, etc.)

@SGaist Thank you for your response I have resolved this issue by changing the graphics driver. I am attaching the link below for others who are facing this kind of problem. https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1060753/am4378-flickering-issue-on-qt-with-eglfs-instance

@pingal said in Component objects cannot declare new properties: But if I add Button element as below, it gives me the mentioned error in the application output AFAIK, Component can hold only 1 root object (eg. Item, Rectangle, Row ect.). It is same a creating a QML file for a component (cf. https://doc.qt.io/qt-5/qml-qtqml-component.html) You should change your code to: Component { id: itemDelegate Item { Button { .. } Row { Rectangle {..} Rectangle {..} Rectangle {..} Rectangle {..} } } }