QML and Qt Quick

@Christian-Ehrlicher Thank you all for your support and assistance. Eventually, I discovered the solution. Originally, it was necessary to add the resource files in the "qt_add_executable" section of the CMakeList file, and set CMAKE_AUTORCC to ON. Although the images couldn't be seen in the QML Designer of Qt Creator, they were displayed perfectly on the Android emulator.

Hello, Though it's a later response, you can try: console.log(video.metaData.value(key)). The key is a fixed number which indicates the metaData keys,like: video.metaData.value(0) //title video.metaData.value(0) //duration etc. When you load a media, the keys will be in array but in random order, you can run console.log(video.metaData.keys()) to get the keys first. I'm not a programmer, so I'm not so surre about if it's the best way to read the MetaData, but it works on Qt6.10

https://github.com/stdware/qwindowkit This is currently the best frameless window lib. It is cross-platform and supports both QWidget and QQuick.

Hi and welcome to devnet, From a quick check, they look pretty neat ! One thing that I would suggest is to translate the comment in the code to English. You'll will reach a wider audience that way.

I do software consulting on various projects, and I personally have written QML by hand while "copying" (the look) from a given Figma project that was handed off to me. I have never used the Figma Qt plugin. FWIW, I have had two different UX designers (experts at Figma) on two different projects comment to me that they gave up on trying to use the Figma Qt plugin (and hence they reverted to writing the QML by hand). Nonetheless, I am now subscribed to this thread because I, too, would love to hear anyone's positive experience or any expert tips that could make it worthwhile to use the plugin.

@Redman My guess is that qmlls can't find the registration details for your "baseclass". Can you provide a reproducer?

I'm not exactly sure what visuals you are going for, but to get it looking like in the picture you might want to look into using a CustomMaterial with cel shading.

There are two main ways of loading meshes in QQ3D, either using balsam https://doc.qt.io/qt-6/qtquick3d-tool-balsam.html or using RuntimeLoader https://doc.qt.io/qt-6/qml-qtquick3d-assetutils-runtimeloader.html. You can also create a custom geometry loader https://doc.qt.io/qt-6/qquick3dgeometry.html but this only provides geometry and not materials or textures.

Finally got the time to finish up the repo collecting the different QML module linking options. Maybe it will help others in the future: https://github.com/KGergo88/QtQMLModuleExamples

@JKSH said in How to customize the attached ToolTip?: The workaround is to call QQuickStyle::setStyle("MyStyle"); in C++ before initializing the QML engine. And if you have a custom style not entirely compliant with Qt Quick Controls or you don't want to switch all your controls, you can hack it by setting the _q_QQuickToolTip (and _q_shared_QQuickToolTip) property of your QQmlEngine to an instance of your ToolTip before loading your QML files (no guarantee it works in future versions). As mentioned in https://qt-project.atlassian.net/browse/QTBUG-107684

@poncho524 said in qml javascript function parameter typing: is there anywhere in the docs that explain when specifying type became acceptable? i can't find it. Not the docs, but this blog post says it was introduced in Qt 5.14: https://www.qt.io/blog/compiling-qml-to-c-annotating-javascript-functions https://www.qt.io/blog/compiling-qml-to-c-annotating-javascript-functions Not that I know of

Fixed it by checking system environment variables, be careful about old QML_IMPORT_PATH and QT_PLUGIN_PATH

@Zapfyr said in QT QML How to chain QAbstractListModel and QSortFilterProxyModel: Limit the output to X items. This sounds like the job of the view. Provide space to display X items, and omit the ability to navigate further.

I did ts_calibrate many times and in ts_test also working only

Indeed, this was a bug. More info here, in case anyone else comes across this: https://qt-project.atlassian.net/browse/QTBUG-145124