QML and Qt Quick

@qwe3 Isn't "import QtQuick 2.0" missing in your QML string? https://doc.qt.io/qt-5/qml-qtquick-image.html

@Markkyboy Thanks for helping out. This helped me to fix the problem [image: a4dab46b-bffa-48e0-a2c3-f89d31b5804c.png]

I ended up copying the org dir to the ~/test-bluez-qt/bin dir so that it is in the default module search path as described at https://doc.qt.io/qt-5/qtqml-syntax-imports.html#qml-import-path I could also have copied the whole module dir to my Qt installation's qml dir in /usr/local/Qt5.15.2/qml, as suggested by the trace output from the above test: QQmlImportDatabase::addImportPath: "/usr/local/Qt5.15.2/qml" The qml test then runs correctly. But still no idea why using the QML2_IMPORT_PATH does not work

@ndias I don't think z value can help when it comes to Popup.

Thank you so much, WasdController is really what you need. The best part is that you can attach not only a camera to it, but also any object, for example a model. Then you can move my cubes with the key. Perhaps it will help someone, everything turned out to be simple there PerspectiveCamera { id: mainCamera position: Qt.vector3d(0, 500, 500) eulerRotation.x: -50 } WasdController { controlledObject: mainCamera } or Model { id: mod01 position: Qt.vector3d(-100, 0, 0) source: "#Cube" scale: Qt.vector3d(1, 0.2, 1) materials: [ DefaultMaterial { diffuseColor: "red" } ] } WasdController { controlledObject: mod01 }

@kshegunov said in Scene3D or Scene3DView visibility set to False breaks all mouse input: @poncho524 said in Scene3D or Scene3DView visibility set to False breaks all mouse input: Huh ... Guess we're not supposed to be using this then ... Look at the comments there's a mention of a workaround you could maybe use. It's probably best not to use some weird hack that is not documented and was just simply discovered by a curious person digging deep in the source. I'm assuming QT Company doesn't really intend these interfaces to be used (except for simple proof-of-concepts and marketing) if the pretty major bugs don't get addressed. :(

@flowery you are so right. I upgraded to Qt 6.2.0 and restart then it solved. Funny but true ?

You can import js files this way: https://doc.qt.io/qt-5/qtqml-javascript-imports.html The javascript implementation in QML is not compatible with node. I think there are objects a node project would expect, but are not implemented. At the least the version in 5.x is not. Not sure what 6.x has in it.

@sierdzio said in using RowLayout defeats width/wrapping.: Can you post an image (or describe in words) what is exactly the output you expect? [image: 2c0eb919-2487-450a-bd8c-8ab7801f658a.PNG] This UI has been cobbled together by many hands, and isn't necessarily the way things should be done, but given the phase of the project, I'm trying to clean things up with a minimum of impact. Apart from a hard-coded font pixelsize, I'm reasonably happy with the fix I posted above. But, I'll keep your comments in mind for the future (though I'm not really much of a fan of layouts in QML).`

I am able to fix the issue by adding the below lines in the main.cpp file // qRegisterMetaType<QQmlListProperty<Person>>("QQmlListProperty<Person>"); qmlRegisterType<Person>("Person", 1, 0, "Person"); qmlRegisterType<BirthdayParty>("BirthdayParty", 1, 0, "BirthdayParty");

I am able to achieve it, using QML vertical header view component of Qt version 5.15.4.

@fcarney Oh shoot, didn't see that that was a link. Thanks!

@aShahba said in Destroying dynamically created objects in a loop: @johngod I know how to have the dialog do self-destruction when accepted signal is emitted. As mentioned in the post, I want to do it in main.qml though. On a sidenote, the problem with self-destruction is that it is only valid if the item is created dynamically. As you can imagine, it is not guaranteed that MyDialog is always created dynamically. Inline components are useful for doing this in a more declarative fashion. Button { Component { id: inlineComponent MyDialog { onClosed: this.destroy() } } onClicked: inlineComponent.createObject(this) }

@SGaist Thanks for clarifying

I just gave a example.You should read what is binding loop.It clearly says you have a binding loop. settings.extendExportFile is bound to textfieldId.text textfieldId.text is bound to settings.extendExportFile Whenever settings.extendExportFile changes which trigger a signal to change textfieldId.text and in turn this trigger a signal to change settings.extendExportFile.This will be happening in a loop, which is known as binding loop.

HI, I found the solution : the android debugger mentionned above was compiled using the ncurses5 library. In recent ubuntu distribs ncurses6 is installed. The solution is to install ncurses5 along with sudo apt get libncurses5. Works perfectly now !