QML and Qt Quick

@Bob64 said in How to make GridView with special zone , which would be free of delegates ?: The only possibly relevant thing I can see in the documentation is the footer property, but it seems that that would position the footer item at the end of, but outside, the grid area. My understanding of what is needed here is a special item fixed at the the bottom right corner of the grid area, within the grid area. It seems like this would be a tricky one to solve. If a dummy item is added at the end of the model, it is not going to be in a fixed position. On the other hand, if something is overlaid on top of the grid area, the grid layout will not know about it and will not try to avoid it. My expectation probably is too much. Using of usual footer is a way(not best because it will be in not grid area). Also i can use model customization in order always to have last delegate as dummy delegate with combination of overlaid Item on top of grid area. Qt: 6.9

It's source: Rectangle { id: confItemsList height: 200 ............ It's loader: Loader { id: loader width: parent.width height: status === Loader.Ready ? item.height : 0 And loader get height 0

Hello. I encountered the same problem, found a solution. It's all about "qrc:/qt/qml". The search for the path "QtQuick/VirtualKeyboard/Styles" starts from there. Accordingly, if you created a resource file not in the root of the application, then you need to add the prefix "/qt/qml/" in the resource file to the directory to your keyboard style. Final structure (using my example): [image: 809f17e6-f89f-4c0f-b67c-92eaddae5718.png] Main.cpp: int main(int argc, char *argv[]) { qputenv("QT_IM_MODULE", QByteArray("qtvirtualkeyboard")); qputenv("QT_VIRTUALKEYBOARD_STYLE", QByteArray("MXTS")); //Just style name, but before create QML engine! J QApplication app(argc, argv); ModelStorage* model = ModelStorage::instance(); QQmlApplicationEngine engine; qDebug() << engine.importPathList(); // for exmaple: QList("C:/git/Torque_sub/TorqueSub/build/Desktop_Qt_6_8_2_MSVC2022_64bit-Debug", "qrc:/qt-project.org/imports", !!!!!"qrc:/qt/qml"!!!!!, "C:/Qt/6.8.2/msvc2022_64/qml") Style.qml: ...... keyboardBackground: Rectangle { color: "red" } ...... Results: [image: f1467529-5950-4066-a296-51f9fe57c507.png] Ref. from src virtual keyboard qt git src: QString stylePath(const QString &name) const { if (name.isEmpty()) return QString(); QStringList stylePathList; stylePathList << QLatin1String("qrc:/qt-project.org/imports/QtQuick/VirtualKeyboard/Styles/Builtin/"); //###### default styles const QStringList importPathList = qmlImportPathList(); //###### get import paths lists // Add QML import path (Note: the QML base dir is usually the last entry in the list) for (int i = importPathList.size() - 1; i >= 0; --i) { const QString stylesPath = importPathList.at(i) + QLatin1String("/QtQuick/VirtualKeyboard/Styles/"); //###### added, so path must: qrc:/qt/qml/QtQuick/VirtualKeyboard/Styles stylePathList += stylesPath; } // Path for backwards compatibility stylePathList << QLatin1String("qrc:/QtQuick/VirtualKeyboard/content/styles/"); for (const QString &stylePath : std::as_const(stylePathList)) { QString filePath = buildStyleFilePath(stylePath, name); bool pathExist = false; pathExist = QFileInfo::exists(filePath); if (pathExist) return buildStylePath(stylePath, name); } return QString(); } Hopefully this will save someone an hour.

The most natural way in QML is a model-view approach. If that at all fits your use case it is usually the cleanest way to go. The UI does not need to be a list (view) as such in order to be driven by a list model. You could use a Repeater-based approach for example. You said you struggled to get the bindings to a list model to work properly. This is almost certainly because of something fairly simple that you are doing wrong, so I would advise persevering with that to find out what the problem is. Reduce it down to a simple case and post it here if you are still struggling.

Yes, I add this dll in release and then svg is work, thanks

Does your system supports avx2? Please provide a minimal compileable example to reproduce the problem. No qml needed for this I would guess.

The same issue. I am trying to run 5.12 codes with QT creator 6.19 on Win11. On Mac this combination is OK. On Win 11 run with QT 5.12 no such issue.

OK, my previous links were for Wayland, so they don't apply to Android. Is this for Android Automotive? If so, then you probably want to use the ActivityView to embed your 3rd-party apps, and you can put your own header and footer around the ActivityView: https://www.qt.io/blog/qt-android-activity-view https://doc.qt.io/QtAndroidAutomotive-6.9/activityview-examples.html Please note: Qt for Android Automotive is a commercial-only product, and is not available to most users on this community forum. If you require further assistance, please contact Qt Support

Hi, Something like the device utilities module ?

@Devopia53 Thank you very much !

@Asperamanca, you'd be as surprised as me, per discuss.kde.org/t/173/17 and discuss.kde.org/t/13920. Although the focuses are on a very specific (albeit important topic), the latter cites some very verbose criticisms from developers. I'm of the hope it's Kirigami's fault, rather than QML's. However, when I've tried pure QML on Plasma, it's looked worse than even Kirigami does. I'll presume that that's because the original creators of Kirigami attempted to style QML initially, and solely after they realised that they couldn't to their satisfaction, created Kirigami. I'd say that this is in comparison to their QStyle, which doesn't require a middleman to style QtWidgets-based applications. However, considering the Union project has recently come to fruition, that might not be true. Though, it might instead be because they need to style QML so heavily that they can't feasibly maintain a QStyle and QQuickStyle. I'll merely wait a little for Union to be released, to see whether the styling improves across platforms. The FluentWinUI3 were a significant improvement, after seeing them in use in NextCloud on Windows 11. It'd be nice if solely one technology were the future, whether QML or QtWidgets.

@SuhasKrishanamurthy said in What is the difference between Canvas3D and View3D in Qt Quick?: I'm a bit confused about when and why one should be used over the other. Qt Canvas3D was deprecated long ago, and has been removed from Qt 6: https://bugreports.qt.io/browse/QTBUG-70510 So, you should use the Qt Quick 3D module (which contains View3D) because it's the one that is actually available and supported in Qt 6. Here is an example: https://doc.qt.io/qt-6/qtquick3d-view3d-example.html Note: Qt Quick 3D is only available under the GPL and Commercial licenses. It is not available under LGPL.

The gui needs to be handled in the main thread - no matter if widgets or qml or whatever.

Thank you, I just tried this: layer.enabled: true layer.smooth: true // tried both true and false here layer.mipmap: true No visual changes, unfortunately.

@GrecKo Thank you, I set setInitialProperties and the errors disappeared

@Christian-Ehrlicher Thank You

You are recreating pkt1secAudio every time. You should really check the lifetime of all your objects.

@Blackzero said in Errors in using ApplicationWindow in Qt Quick Design: @JKSH Yes, the application can still run. I hope that in the future, Qt Quick Plugin will support ApplicationWindow. There is an open change request for this. You can watch/vote for it: https://bugreports.qt.io/browse/QDS-10914 I forgot: It should also work if you use Window instead of ApplicationWindow. But the latter is a lot more feature-rich.