QML and Qt Quick

@JKSH We are targeting Qualcomm 6155 board, with Android 14. Yes we are managing 3rd party apps as well. We want our custom header and footer should always be present and visible to user. And centre part will be available to show all apps screen, can launch any QT or 3rd party application in between area.

@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.

@SanderVc said in Sudden QML system issues not solved by reinstall: The issues I am seeing since then: "QtObject is not a type", referring to the QtObject object type which I thought was pretty fundamental to Qt Quick; "Non-existent attached object", referring to a qml line using "Component.onCompleted:" - suggesting the "Component" attached object does not exist. Do you see those when trying to run your application? Or when trying to edit your application in Qt Creator? (Knowing the difference is important, because they have very different root causes)

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.

@Bob64 I want to do it like in the picture but I don't know how! [image: c8fc3b40-e5df-4f27-9cfe-919d50d3f3e2.png]

@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.

@Mucip said in Qt 6.9 and QML harmony?: Program is working but no intellisense. If you use setContextProperty() or qmlRegister*() functions, then the classes are only registered AFTER the program starts running. That's why code completion (Intellisense) doesn't work -- because your classes have not been registered so the QML tools can't see your classes. The documentation contains a warning about the problems of context properties: https://doc.qt.io/qt-6/qtqml-cppintegration-contextproperties.html Instead, use the QML_ELEMENT + QML_SINGLETON macro with qt_add_qml_module() to register your class automatically when building your project. Then, code completion can work. The "QML Video" example (https://doc.qt.io/qt-6/qtmultimedia-video-qmlvideo-example.html ) shows how to do this with its VideoSingleton class: https://code.qt.io/cgit/qt/qtmultimedia.git/tree/examples/multimedia/video/qmlvideo/qmlvideo/videosingleton.h?h=6.9 https://code.qt.io/cgit/qt/qtmultimedia.git/tree/examples/multimedia/video/qmlvideo/qmlvideo/CMakeLists.txt?h=6.9 For more information about integrating C++ and QML, see https://doc.qt.io/qt-6/qtqml-cppintegration-overview.html

Hi, From a quick search it's seems there's an android specific private API that you can leverage. Please note the warning that comes with it.

This tells me nothing - we need a minimal, compilable example to reproduce the problem and you have to use a proper memory checking tool.

@raven-worx I have followed all this but i am getting a wired thing displayed on my screen by following this process. The back ground contians some UI from my page but when the keyboard is poping up it is looking like this . [image: 2cba5105-17fb-4491-ad5f-5ed0a3ba9fc9.png]

As an alternative, we are using Icons to color svg images meant for button or action icons : https://doc.qt.io/qt-6/qtquickcontrols-icons.html#icon-themes

Are you using a QGuiApplication or a QApplication? You should be using the latter.

@JKSH Thank a lot for your concise reply—it really solved my problem! ：） Although I didn’t set the QML_IMPORT_PATH, I had bundled all dependencies into the .../target/debug folder for debugging convenience. Qt then loaded QML modules from there by default, but since QtCharts was missing, a runtime error occurred. After deleting everything except third-party libraries in the folder and rebuilding, Qt now loads modules from the installation directory, and everything works fine. Your explanation gave me a much clearer picture of how Qt handles QML module loading, especially the fallback behavior—I am truly grateful!