QML and Qt Quick

As @rrlopez already wrote, use the file:// scheme and you can access the files.

@april_heard I would say, this looks like a job for a listview. You can define your own delegate and than elide it. That way only the display is changed, the underlying data is unchanged.

understood, It is not support

Thanks Dheerendra and sierdzio. Issue is resolved. @sierdzio , yes you are correct, it is Qt issue in libQt5Qml.so.5.12.3 and it is fixed in libQt5Qml.so.5.12.5. Thanks, Kadappa Pujari

It really works! Thank you, IntruderExcluder, GrecKo.

The example below works fine both for text and files (Linux Mint with Nemo as file manager): DropArea { anchors.fill: parent onDropped: { console.log(drop.text); } }

@VeNToR I am really sorry but I don't think I understand well enough what you are trying to achieve to be able to make any sensible suggestions.

@LeLev In the main.qml file I have navigation elements (e.g. Drawer) and other UI elements (e.g. tabs, splitter etc.) and inside the main.qml I need to display MyRect.qml (it holds the VtkFboItem). I also need to connect the VtkFboItem with the C++ object to display AND interact with 3D graphics. ApplicationWindow { id: root Rectangle { id: screenCanvasUI anchors.fill: parent Drawer{ …….. } MyRect{ } } Button { id: openFileButton text: "Add Model" …………... } FileDialog {.....} }//end:ApplicationWindow /MyRect.qml file: Item{ VtkFboItem { objectName: "vtkFboItem" anchors.fill: parent MouseArea { ............. } }//end: VtkFBO }//end: Item //main.cpp file ....... // Load main QML file engine.load(QUrl("qrc:/resources/main.qml")); // Get reference to the QVTKFramebufferObjectItem created in QML QObject* rootObject = engine.rootObjects()[0]; m_vtkFboItem = rootObject->findChild<QVTKFramebufferObjectItem*>("vtkFboItem"); QObject* rootObject = engine.rootObjects()[0]; m_vtkFboItem = rootObject->findChild<QVTKFramebufferObjectItem*>("vtkFboItem"); if (m_vtkFboItem) { m_vtkFboItem->setProcessingEngine(m_processingEngine); connect(m_vtkFboItem, &QVTKFramebufferObjectItem::rendererInitialized, this, &CanvasHandler::startApplication); ..................... } app.exec(); In the above scenario, how should I be able to find and connect to the vtkFboItem from the main.cpp? Is there any other way to achieve this apart from the objectName? I have attached here a screenshot of the final UI that I am trying to achieve.[image: 18b7b2b6-55d7-41b3-ae0a-fb399fe27e30.PNG]

i don't understand sorry. Image has no color property if you have 2 images each with different color then change the source property to show one or the other

@rrlopez Thanks for your answer.

@Bob64 I see that you've received the clarifications you need for this particular issue. If you'd like to further your understanding, see this article: https://doc.qt.io/qt-5/qtqml-syntax-propertybinding.html

Ah, seems it is working fine with Q_INVOKABLE added to the getter method, and using engine.rootContext()->setContextProperty public: Q_INVOKABLE Person* getGuestByName(QVariant name); ..... Person* BirthdayParty::getGuestByName(QVariant name) { QList<Person*>::iterator i; for (i = this->m_guests.begin(); i != this->m_guests.end(); ++i) { if ((*i)->name() == name) { return *i; } } return nullptr; } //main.cpp BirthdayParty parties; QQmlApplicationEngine engine; engine.rootContext()->setContextProperty("parties", &parties); //example.qml Button { id: jack_button property Person boy: parties.getGuestByName("Jack Smith") }

@J-Hilk I haven't tried substitution. But as the QTBUG-67698 last comment says , the exact same code works fine until qt<5.9.

What are the roles of your VideoOptions QALM ? Can't you have a role returning your Format QALM? It's also kinda hard to help you further since this really depends on your data structure and on how you store your data underneath the model.

@JonB This is correct. In theory there is a windows api for this. I started down that rabbit hole and quickly backed out of it because it's a lot of work to track down the correct process. I may have found a solution, but I'm not happy with it: powershell -ExecutionPolicy bypass -Command "add-type -AssemblyName Microsoft.VisualBasic; [Microsoft.VisualBasic.Interaction]::AppActivate(process->processId)" Call that from a QProcess::start(), depending on how finicky your system is you may need to break it into the "powershell" command and a QStringList of arguments, but that does pull the child process to the front.